list_projects

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'List all projects in the account.' It does not disclose pagination behavior, the effect of the limit parameter, or that 'all' may not be fully returned in a single call when the account exceeds the maximum limit.

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, front-loaded sentence with no filler or redundant information. It is concise, though slightly too sparse given the potential mismatch between 'all' and the limit parameter.

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?

For a simple list tool with one optional parameter, the description and schema provide a workable baseline. However, the lack of pagination or limit context, especially given the 'all' wording, leaves an agent uncertain about behavior when more than 100 projects exist.

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 coverage is 100%, so the single limit parameter is fully documented in the schema. The description adds no parameter-level detail, which is acceptable because the schema already provides the default and maximum values.

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 uses a specific verb ('List') and a clear resource ('all projects in the account'), making the tool's function immediately obvious. It naturally distinguishes itself from siblings like get_project, create_project, and update_project by focusing on account-wide enumeration.

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 implies the tool is for retrieving all projects, which provides clear context for account-level listing. However, it does not explicitly say when to use this instead of get_project, nor does it mention any exclusions or pagination caveats.

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