projects_list

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

With no annotations, the description fully explains behavior: it is a read-only listing operation. It lists all return fields including statuses (Initializing/Provisioning/Active/Suspended/Terminated/Error), which is beyond the input schema. No contradiction.

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 efficient sentences with no wasted words. The main action is front-loaded, and the second sentence packs necessary details (return fields, prerequisites, usage flow) in a structured manner.

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 no output schema, the description comprehensively covers return values (fields and statuses) and prerequisites. It also integrates with sibling tools, providing a complete usage context for a list operation.

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 100%, and the parameter's description already states it defaults to the active account. The tool description does not add new meaning about the parameter's format or constraints beyond the schema.

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 the projects (provisioned backend instances) in a billing account,' using a specific verb and resource. It distinguishes from sibling tools by mentioning that the output is used with 'projects_use' and 'projects_delete'.

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?

Explicitly states prerequisites: 'Requires platform login and an active billing account (set one with 'accounts_use').' Provides clear context on when to use: 'Use this to find a project's id before connecting with 'projects_use' or removing it with 'projects_delete'.'

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