projects_list

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

No annotations; description only mentions grouping by freshness but doesn't explain return format, whether it lists projects or details, or any side effects. Lacks operational clarity.

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 are short and front-loaded with the purpose, but they omit critical operational details. Conciseness is acceptable but at the cost of completeness.

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?

Given a simple schema with one optional parameter and an output schema, the description should clarify what is returned and how 'freshness' is determined. It falls short, leaving gaps about usage.

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 sole parameter 'limit' has no description in schema (0% coverage). The description does not mention or explain its purpose, leaving the agent to infer from defaults and constraints.

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 hints at listing collab projects sorted by freshness, but the verb 'list' is implicit. It's not as explicit as sibling tools like 'tasks_list'. The purpose is somewhat clear but could be more direct.

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 on when to use this tool over alternatives like project_chats or project_read. No context for prerequisites or exclusions.

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