list_interventions

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

Annotations already provide readOnlyHint=true, so the description adds no additional behavioral context beyond that. It does not mention pagination, ordering, or any side effects, which are common for list tools. The description is minimal.

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 short, structured as a header followed by a bullet-like list of parameters. Each sentence is purposeful and provides necessary information without fluff. It is well-organized and easy to parse.

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 presence of an output schema and optional parameters, the description covers the essential functionality. However, it lacks context on result ordering, pagination behavior (despite a limit parameter), and the scope of 'supervisor interventions'. It is adequate but not comprehensive.

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 0%, so the tool description must compensate. It provides one-line explanations for each parameter (e.g., 'Filter by mission.'), which adds meaning beyond the property names. However, descriptions are brief and lack details like accepted formats or constraints, but they are sufficient for basic understanding.

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 'List supervisor interventions,' which is a specific verb and resource. It distinguishes from sibling tools 'get_intervention' (singular) and 'create_intervention' (create). However, it does not elaborate on what an intervention is, but the intent is clear.

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?

No guidance on when to use this tool versus alternatives like 'get_intervention' or 'create_intervention'. There is no mention of typical use cases or exclusions, leaving the agent to infer context.

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