list_projects

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

Description adds default output behavior ('compact summaries') and effect of verbose parameter, but with no annotations, more detail on sorting, pagination, or error handling would be needed.

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, no wasted words – every sentence adds value.

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?

Adequate for a simple browse tool but lacks details on return structure (beyond hint from verbose), sorting order, or pagination; no output schema to compensate.

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?

Description adds purpose to keyword and category (filters) and context to verbose (compact vs full), partially compensating for 50% schema coverage; but lacks constraints or formats for 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?

Description clearly states verb 'browse' and resource 'inferred projects' with filtering dimensions (keyword, category, recency), distinguishing it from siblings like find_commits or get_episode.

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 explicit guidance on when to use this tool versus alternatives; no 'use this when' or 'use X instead' statements despite many sibling tools.

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