get_diagram_info

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

Discloses that the tool provides node ids, labels, component types, and connection topology, implying a read-only operation. No annotations exist, but the description sufficiently covers expected 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?

Two sentences, front-loaded with purpose and usage. No superfluous information; every word contributes value.

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 the output schema exists, the description appropriately lists the summary contents (node ids, labels, etc.) and provides sufficient context for a single-parameter read 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 100% with a clear description for file_path. The tool description adds no additional parameter details beyond confirming the file is an existing Excalidraw diagram, meeting the baseline.

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 retrieves a structured summary of an existing Excalidraw diagram, distinguishing it from siblings like 'create_diagram', 'modify_diagram', and 'mermaid_to_excalidraw'.

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 calling this tool BEFORE modify_diagram to understand current state. While it doesn't specifically exclude other scenarios, the context is clear for appropriate use.

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