list_projects

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

Without annotations, the description only explains the include_completed flag and pagination parameters. It does not disclose sorting order, maximum limit, or whether the tool modifies any state (it likely does not).

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 very concise: a one-sentence summary followed by parameter documentation. No unnecessary information.

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?

The description covers parameters adequately but lacks behavioral context like default ordering, scope (all workspaces?), or any performance considerations. Since an output schema exists, return values are not needed.

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 three parameters (include_completed, limit, offset) are explained with default values and behavior (e.g., default false means active only), compensating for the 0% schema description 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?

The description clearly states the tool lists projects and defines what projects are (multi-step tasks with sub-tasks), distinguishing it from sibling tools that list tasks, today's tasks, etc.

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 guidance is provided on when to use this tool versus other list tools or search functions. It does not specify that it lists all projects (likely across workspaces) or any exclusion criteria.

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