list-statuses

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

No annotations are provided, so the description carries the full burden. It does not disclose whether the tool is read-only, whether pagination is handled, or any details about the active filter (though it exists in the schema). The description oversimplifies the tool's behavior.

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 a single sentence that is concise and front-loaded with the key action. However, it is too brief and omits important details that could have been added without sacrificing conciseness, such as mentioning the active filter or pagination.

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?

With 4 parameters and no annotations or output schema, the description is inadequate. It only covers one parameter (status_type) and does not address pagination, active filtering, or the per-page limit. A more complete description would include these details to help an agent use the tool correctly.

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?

All parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description only adds meaning for 'status_type', which is already documented in the schema. No additional value is provided for other parameters like 'page' or 'active'.

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 all statuses' with the verb 'list' and resource 'statuses', and mentions optional filtering by status type, which adds specificity. However, it does not differentiate from sibling tools like 'get-statuses-by-type' or 'get-status', which could cause confusion for an AI agent.

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 no guidance on when to use this tool versus alternatives such as 'get-status' or 'get-statuses-by-type'. It lacks context about when to apply the filter or any exclusionary criteria.

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