list_diagrams

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

No annotations are provided, so the description carries full burden. It describes default sort behavior and filtering but does not disclose potential side effects, permissions, pagination, or rate limits. Adequate for a list tool but lacks deeper behavioral context.

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, front-loaded with main purpose, each sentence earning its place. No redundancy or fluff.

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 and simple parameters, the description covers core usage, filtering, sorting, and a key workflow (avoid duplicates). Could mention pagination or limits, but not essential.

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 adds value by explaining when to use each parameter (e.g., 'use when looking for a named diagram' for `q`, 'omit unless the caller already has the user id' for `owner`, and 'use this to find the most recently changed diagram' for sort updated, plus references list_folders for folderId). This surpasses the schema descriptions.

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 diagrams in the configured Space' with default behavior (every folder, newest first). It distinguishes from siblings by mentioning use before create_diagram and preferring update_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?

Explicitly advises to use before create_diagram to avoid duplicates, and suggests preferring update_diagram if a diagram exists. Also provides guidance on filtering with `q` and sorting with `sort`.

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