convert_diagrams_read

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

With no annotations, the description carries the full behavioral burden. It usefully discloses batch behavior, file-type scope, output format, and that results are returned to the caller. However, it never explicitly states the operation is non-destructive/read-only (only the name's 'read' hints at it), and it does not warn that batch-converting 'all' workspace files could produce very large context output.

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?

A single sentence with zero filler: action and scope are front-loaded, followed by output format and return semantics. Every element earns its place, and no information is repeated from the schema.

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 tool with only 2 optional parameters, no output schema, and no annotations, the description supplies the core facts: what it scans, what it produces, and where the result goes. Remaining gaps — no explicit non-destructive statement, no failure/skip semantics for unparseable files, no per-file response structure — are relatively minor given the 'content directly as AI context' framing.

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% — both patterns and diagramType already have clear descriptions in the schema. The tool description adds only marginal context (e.g., the default 'all workspace files' behavior implied by 'Batch scan and convert all'), so the baseline 3 applies; it neither compensates for gaps nor adds meaningful parameter insight.

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 action ('Batch scan and convert'), specific resources (workspace .xml/.drawio diagram files), and explicit output (Mermaid Markdown). The clause 'returning their content directly as AI context' signals a read-style operation that contrasts with the write sibling, making the purpose unambiguous.

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?

Usage is implied — this is the tool for getting diagram content into AI context as Mermaid — but there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as convert_diagrams_write for persisting output or list_diagrams for merely enumerating files. An agent must infer selection criteria from the name and output framing.

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