list_missions

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

The description mentions that it returns summaries with specific fields, giving some behavioral insight. However, no annotations are provided, so the description carries the full burden, but it does not disclose performance characteristics, rate limits, or whether the list is paginated or limited. With zero annotations, a 3 is appropriate as it adds meaningful context about return content.

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 two sentences, efficiently providing purpose and a usage pointer to a sibling tool. It is front-loaded with the core action. Minor improvement could be more concise by merging purpose and summary, but overall it's well-structured.

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 no output schema and simple parameters (none), the description covers the essential aspects: what it lists (missions for authenticated user) and what it returns (summaries with fields listed). It lacks details on ordering or pagination, but for a straightforward list tool, it is reasonably complete.

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?

The input schema has no parameters (0 params, 100% coverage), so the description cannot add parameter semantics. Given zero parameters, a baseline of 4 is appropriate since there is no need to describe parameters.

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 states 'List all drone missions for the authenticated user' with a clear verb (list) and resource (drone missions). It distinguishes itself from sibling 'get_mission' by noting that it returns summaries and refers to get_mission for full waypoint details.

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 mentions authentication context ('for the authenticated user') and explicitly tells when to use the alternative tool ('Use get_mission with a specific ID for full waypoint details'). However, it does not mention when not to use this tool or other alternatives like creating or duplicating missions, which are among siblings.

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