quire.listStatuses

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

Annotations already declare readOnlyHint=true, so the description's confirmation of 'list' adds no new behavioral traits beyond that. The mention of default statuses is a minor additional context, but overall the description does not significantly enhance transparency beyond annotations.

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?

Two sentences, no wasted words. First sentence states core purpose. Second sentence adds return structure and notes about defaults. Extremely efficient and 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?

Description adequately covers purpose, return format, and default statuses. No output schema, but the description mentions the return structure. Could potentially mention if pagination is needed, but for statuses it's likely unnecessary. Overall complete for a simple list tool.

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 provides a description for the single parameter (projectId). The tool description does not add any further semantics beyond what the schema already states. With 100% schema coverage, baseline is 3.

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?

Description clearly states verb (list), resource (custom statuses), and scope (in a project). It specifies the return type (array of status objects with value, name, color). This distinguishes it from sibling tools like quire.getStatus (single status) and quire.createStatus (mutation).

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?

While not explicitly stating when not to use, the purpose is clear: listing all statuses in a project. Given sibling tools like quire.getStatus, it's obvious that this is for bulk retrieval. No exclusion criteria are needed as it's a simple read operation.

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