list_diagrams

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

No annotations are provided, so the description carries the full burden. 'Discover' implies a read-only search operation, and it specifies scope (workspace) and approach (glob patterns). However, it does not explicitly state that the tool returns a list of file paths, does not modify anything, or how defaults behave when no patterns are supplied.

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 focused sentence that front-loads the purpose, resource type, file extensions, and search method. No unnecessary words or redundant information.

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 full schema coverage, the description is mostly complete. It clearly communicates what files are searched and how. The main gaps are the absence of explicit return-value information and default pattern behavior, but these are minor for this type of 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 description coverage is 100%, and both parameters (patterns and ignore) already have meaningful descriptions. The tool description reinforces that glob patterns are involved and that .xml/.drawio files are the targets, but it does not add substantial new meaning beyond the schema.

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 uses a specific verb ('Discover'), names the resource ('Draw.io architecture diagram files'), and lists the relevant file extensions and method ('glob patterns'). This clearly distinguishes it from sibling tools like convert_diagrams_read and convert_diagrams_write, which are about conversion rather than discovery.

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 gives clear context: use this when you need to find Draw.io diagram files in the workspace by glob patterns. It does not explicitly mention alternatives or exclusions, but the purpose is distinct enough from the convert siblings that an agent can infer when to choose this tool.

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