List my diagrams

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

With readOnlyHint=true in annotations, the description adds value by disclosing pagination behavior (newest first, cursor-paginated) and the return shape (id, title, cloud, type). It does not contradict the annotation and provides useful behavioral context beyond what the annotation already conveys.

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, well-structured sentence that front-loads the action and includes essential details (ordering, pagination, returned fields) without any filler. Every word earns its place.

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 listing tool with two optional parameters and no output schema, the description is complete: it explains the scope ('your diagrams'), ordering, pagination, and return fields. The readOnlyHint annotation covers safety, and the schema covers parameter details, so nothing important is missing.

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?

The input schema already provides full coverage (100%) with clear descriptions for both parameters (limit as page size with default, cursor as next_cursor from previous call). The description only mentions 'cursor-paginated', which adds no new semantics beyond what the schema already states.

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 the tool's purpose with a specific verb ('List') and resource ('your diagrams'), and distinguishes it from sibling tools like get_diagram by indicating it returns multiple diagrams. It also specifies ordering and returned fields, leaving no ambiguity about the tool's function.

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 usage by saying 'List your diagrams', but does not explicitly state when to use this tool versus alternatives such as get_diagram or list_versions. There is no mention of exclusions or specific contexts where a different tool would be more appropriate.

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