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

No annotations; description carries full burden. It mentions pricing and side-by-side comparison, but omits read-only status, permission requirements, and return format details (e.g., pagination). For a read tool this is a notable gap.

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, front-loaded with the core action, no unnecessary words.

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 simple one-parameter listing tool with no output schema, the description conveys enough: it returns a comparison of priced missions for a city. However, absence of any safety or return-shape detail leaves minor incompleteness.

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% and the lone parameter has a description. The description adds no additional meaning about the 'city' parameter beyond what the schema provides.

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?

States that it returns every mission priced for one city, enabling comparison. Clearly a city-scoped listing, distinguishable from list_missions (all missions) and quote_mission (single mission price), though siblings are not named.

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?

Implies comparison use case ('so the user can compare what is possible there') but does not state when to use this versus list_missions or quote_mission, nor any prerequisites. Guidance is contextually implied rather than explicit.

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