List projects

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

No annotations are provided, so the description carries full burden. It states 'List all projects' but fails to disclose pagination behavior (limit, cursor), read-only nature, or any restrictions (e.g., rate limits). The tool might not list all projects if paginated, which contradicts the plain reading.

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 a single sentence, concise and front-loaded with purpose. It contains no wasted words, but could benefit from a bit more detail without becoming verbose. It is appropriately sized for a simple list tool.

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 the tool has two pagination parameters and no schema descriptions, the description is incomplete. It does not cover what the output contains (though an output schema exists), pagination behavior, or the Enterprise requirement's practical implications. More context is needed for effective use.

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 description coverage is 0%, and the description does not explain any parameters. The limit and cursor parameters are left entirely undocumented, despite being crucial for pagination. The description adds no meaning beyond the schema's bare structure.

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 'List all projects (Enterprise feature).' It uses a specific verb 'List' with the resource 'projects', and distinguishes from sibling tools like create_project, delete_project, and update_project by focusing on listing. The Enterprise note adds clarity.

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?

The description notes 'Enterprise feature,' which indicates when it's available. However, it does not provide explicit guidance on when to use it vs alternatives (e.g., other list tools) or when not to use it. The sibling list tools are for different resources, so differentiation is implicit.

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