eve-online-traffic-mcp

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

Annotations already indicate read-only and open-world hints, but the description adds valuable context by specifying the data sources ('ESI and SDE APIs') and the types of information included ('security status, connections, and celestial objects'), which helps the agent understand the tool's behavior beyond the annotations. No contradictions with annotations.

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, well-structured sentence that efficiently conveys the tool's purpose, sources, and key data types without unnecessary words. It is front-loaded with the main action and includes all essential information.

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 tool's complexity (fetching comprehensive data from multiple APIs) and the absence of an output schema, the description adequately covers what the tool does and the data included. However, it could benefit from mentioning response format or limitations, though annotations provide some safety context.

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 description coverage is 100%, so the schema fully documents the 'systemIds' parameter. The description does not add any parameter-specific semantics beyond what the schema provides, such as format details or examples, but it implies the tool processes multiple systems, aligning with the schema.

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 clearly states the specific action ('Get comprehensive solar system information') and resources ('from both ESI and SDE APIs'), distinguishing it from siblings like 'get_system_combat_stats' or 'solar_system_name_to_id' which focus on specific aspects or conversions. It explicitly mentions the scope includes 'security status, connections, and celestial objects'.

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 clear context for when to use this tool (for comprehensive solar system data), and the input schema includes guidance to use 'solar_system_name_to_id' for name conversions. However, it does not explicitly state when not to use it or compare it to alternatives like 'get_system_combat_stats' for combat-specific data.

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