List Projects

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

Annotations already mark as read-only, non-destructive, idempotent, open-world. Description adds pagination behavior and the 'lightweight' nature with tasks_count, which is useful 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 concise sentences, front-loaded with core action and result, then usage guidance. No extraneous words.

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 no output schema, description mentions key fields (tasks_count, paginated list). Covers main use case adequately for a list tool. Could mention that it returns only lightweight info, not full project details.

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 descriptions cover 100% of parameters. Description does not add significant extra meaning for parameters; pagination hint is already in schema descriptions. Satisfies baseline for high coverage.

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?

Specific verb 'List' plus resource 'Projects', description details paginated lightweight list with tasks_count. Distinguishes from sibling tools like aiproject_get_project and aiproject_create_project by stating 'Use this before selecting a project ID'.

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?

Directs use before task operations for selecting a project ID, but could be clearer about when not to use (e.g., when needing full project details). Still provides clear context.

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