eve-online-traffic-mcp

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

Annotations provide readOnlyHint=true and openWorldHint=true, indicating this is a safe read operation with potentially large data scope. The description adds value by specifying the tool is 'useful for finding trading hubs, reprocessing facilities, or other specialized services,' which gives context about typical use cases. However, it doesn't disclose additional behavioral traits like rate limits, authentication needs, or what happens with no results, leaving room for improvement.

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 highly concise and front-loaded: two sentences that directly state the purpose and usage context without any wasted words. Every sentence earns its place by providing essential information, making it easy for an AI agent to quickly understand the tool's role.

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 (4 parameters with nested objects, no output schema), the description is reasonably complete. It covers the core purpose and usage context, and annotations provide safety and scope hints. However, without an output schema, the description could benefit from mentioning what the tool returns (e.g., a list of stations with services), but this is a minor gap given the clear annotations.

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 all parameters. The description doesn't add any parameter-specific information beyond what's in the schema, such as explaining service name formats or search area constraints. This meets the baseline of 3 since the schema does the heavy lifting, but no extra value is provided.

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 tool's purpose: 'Find stations that offer specific services within specified systems or regions.' It includes the verb 'find' and resource 'stations' with the key constraint of 'specific services' and location scope. However, it doesn't explicitly differentiate from sibling tools like 'get_station_services' or 'find_nearest_trade_hub,' which reduces it from a perfect score.

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: 'Useful for finding trading hubs, reprocessing facilities, or other specialized services.' This gives practical examples of use cases. However, it doesn't explicitly state when not to use it or name alternatives among the sibling tools, such as 'find_nearest_trade_hub' for simpler trade hub searches.

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