eve-online-traffic-mcp

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating safe read operations with potentially incomplete data. The description adds value by specifying what data is returned ('security status and constellation information'), but doesn't disclose behavioral traits like rate limits, pagination, or error conditions beyond what annotations provide.

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?

Single sentence efficiently conveys the core purpose with zero wasted words. Front-loaded with the main action ('Get a comprehensive list'), followed by scope and data details. Every element earns its place.

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?

For a read-only tool with good annotations and full schema coverage, the description provides adequate context about what data is returned. However, without an output schema, it could benefit from more detail about return format (e.g., structure of system objects, pagination). Still, it's mostly complete for its complexity level.

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%, with the parameter fully documented in the schema (regionIds array with numeric IDs, max 10 items, name conversion requirement). The description doesn't add any parameter semantics beyond what's already in the schema, so baseline 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 clearly states the verb ('Get') and resource ('comprehensive list of all solar systems in specified regions') with specific attributes ('security status and constellation information'). It distinguishes from siblings like 'solar_system_info' (single system details) and 'region_info' (region-level data) by focusing on bulk system listing within regions.

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 implies usage context ('in specified regions') and the input schema provides explicit guidance to use 'region_name_to_id' tool first for name conversion. However, it doesn't explicitly state when NOT to use this tool versus alternatives like 'find_systems_in_range' or 'solar_system_info', though the scope difference is clear from the purpose.

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