list_mission_templates

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The phrase 'List the mission templates available to your agent' clearly indicates a read-only, non-destructive operation and scopes the results to the agent's context. There are no hidden side effects hinted at, and none are needed for a simple listing tool.

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?

One concise, front-loaded sentence that conveys both the action and the output scope. Every word carries meaning, with no filler or redundant information.

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 zero-parameter list tool, the description is largely complete: the agent knows what is listed and what information is returned. The absence of an output schema means the exact response format is not defined, but the description's promise of template names and parameters is sufficient for an agent to call this tool successfully.

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 and 100% schema description coverage, so the schema fully documents what is accepted. With 0 parameters, the description earns a baseline 4 and doesn't need to compensate for any undocumented 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 a specific verb ('List') and resource ('mission templates'), and adds that it returns the parameters each template accepts. This clearly identifies the tool's purpose, though it does not explicitly differentiate it from sibling tools like list_missions or discover_missions.

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 this tool should be used when an agent needs to know which mission templates and their accepted parameters are available. However, it does not provide explicit guidance on when to use this tool versus alternatives such as list_missions, discover_missions, or start_mission.

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