List Project Tools

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds value beyond annotations by specifying the API endpoint (GET), pagination behavior (page, per_page, pagination metadata), and that it returns a JSON array. No contradictions with annotations.

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 four sentences, front-loaded with the main purpose. It efficiently includes usage guidance, pagination details, and API reference. Every sentence adds value without redundancy.

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 mentions a paginated JSON array with metadata, but does not describe the structure of individual tool records. For a listing tool, this is a gap; however, the annotations and schema are strong. It provides enough context for basic use but lacks detail on response fields.

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 baseline is 3. The description mentions pagination parameters and required project_id, but does not add significant meaning beyond the schema descriptions. It does not elaborate on filter parameters or their expected 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 clearly states it returns all tools for a project, with pagination and filtering. It specifies the verb 'Returns' and the resource 'Tools available to the provided Project'. However, it does not explicitly differentiate from the sibling `list_project_tools_v1_0_2`, but the version in the name provides implicit distinction.

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 provides explicit usage guidance: 'Use this to enumerate Project records when you need a paginated overview, to find IDs, or to filter by query parameters.' This informs the agent when to invoke it. It does not mention when not to use it or alternatives, but the context is clear.

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