get_character_info

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full burden. It only states 'Retrieve information' without disclosing read-only behavior, authentication needs, rate limits, or error handling (e.g., if the character ID is invalid). This leaves significant gaps for the agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence of 8 words, which is appropriate for a simple tool. It is front-loaded and contains no unnecessary text, but could benefit from structure (e.g., bullet points for return data).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema, the description should at least hint at the kind of information returned (e.g., character name, corporation, age). It does not, leaving the agent uncertain about the tool's output. This is a significant gap for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single parameter 'id', with a description that mirrors the schema. The tool description adds no extra semantic value beyond what is already in the schema, so a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the verb 'Retrieve' and specifies the resource 'information about a specific character', which clearly indicates the tool's basic function. However, it lacks specificity on what type of information is returned, making it less distinguishable from sibling tools like character_blueprints or character_location.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as character_online or character_ship. Without context, an agent may not know that this tool retrieves general character info, while sibling tools cover specific aspects.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.