List Project Document Custom Tags

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds valuable behavioral details: pagination support with page and per_page, pagination metadata, required project_id, and the exact endpoint URL. This context enhances understanding beyond the 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 brief and front-loaded with the primary purpose. It includes necessary details without superfluous text. The endpoint specification is slightly technical but not overly verbose.

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?

While the description covers pagination, required parameters, and filtering, it provides incorrect information about the return type (Documents instead of Document Custom Tags). Without an output schema, this error leaves the agent uncertain about the actual returned objects, reducing completeness.

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?

Input schema coverage is 100% with descriptions for all four parameters. The description reinforces that page and per_page control pagination and that project_id is required. It adds minimal extra meaning, so a baseline 3 is appropriate.

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 states 'Return a list of Document Custom Tags' which matches the tool name, but then contradicts itself by saying 'enumerate Documents' and 'Returns a paginated JSON array of Documents', confusing the resource type. This muddles the purpose and reduces 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 advises using this tool for paginated overview, finding IDs, or filtering by query parameters. It does not compare to siblings, but no sibling directly duplicates this listing capability, so the guidance is clear and appropriate.

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