list_projects

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that it returns results in 'Capsule's default order (no sort parameter is supported here)', which is useful but not extensive. Some behavioral aspects like pagination behavior are not disclosed, though annotations cover the safety profile.

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, front-loaded with purpose. The first sentence states the core function, the second adds usage guidance. No extra words, every sentence earns its place.

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?

While the description covers purpose and usage guidance well, it lacks parameter details and pagination info. Given no output schema and 4 parameters, the agent might not know how to use page/perPage or embed. However, the alternative tool is correctly suggested for complex queries, providing some completeness.

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 coverage is low (25%), with only 'embed' described in the schema. The description mentions 'optionally filtered by status' but adds no detail on 'page', 'perPage', or 'embed' format. It does note the absence of sort, but overall adds minimal meaning beyond what the schema provides.

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 the verb 'list' and the resource 'projects (cases)', with optional filtering by status. It distinguishes itself from the sibling 'filter_projects' by noting what it cannot do (sorted queries), making the purpose very specific.

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?

Explicitly tells when not to use this tool: 'For structured queries ... use filter_projects instead.' Also notes the lack of sort parameter, providing clear guidance on appropriate usage vs. alternatives.

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