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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description still adds real behavior: newest-first ordering, AND semantics for multi-word queries, and cursor-based pagination. It omits auth/permission requirements and any rate-limit or empty-result behavior.

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?

Three sentences, each earning its place: what it returns, how to filter, how to paginate. Front-loaded with the core action and no redundant restatement of the title.

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?

No output schema exists, so the description correctly enumerates returned fields and explains pagination and ordering. Together with the schema's bounds on limit, an agent has everything needed to call and page through this tool.

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 67% (query and cursor documented; limit only bounded by default/min/max). The description adds meaning beyond the schema by clarifying that query matches titles containing every word (AND, not OR) and that cursor is the value returned by the previous page.

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?

States a specific verb and resource ('List the diagrams saved to your Volley account'), plus the sort order (newest first) and the fields returned (id, title, visibility, short link). This clearly separates it from sibling list_collections (different resource) and from single-item tools like get_diagram.

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?

Gives concrete usage guidance for two of three parameters: 'Pass query to find diagrams whose title contains every word' and 'pass the returned cursor to get the next one.' It does not say when to prefer this over check_diagram/get_diagram or state exclusions, so it falls short of the explicit when/when-not bar.

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