read_diagram

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

With no annotations provided, the description carries the behavioral disclosure burden. It conveys a read-only operation through 'Read and analyze' and specifies what kind of output to expect: a description of shapes, connections, and colors. It does not expand on error cases or permissions, but for a simple read tool this is reasonably transparent.

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 compact and front-loaded with the core purpose, followed by useful output and argument details. There is minor redundancy between the opening 'Returns a structured description...' and the later 'Returns: Human-readable description...', but overall the structure is clear and efficient.

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 one-parameter read tool, the description covers the action, the input file type, and the return value in enough detail for an agent to call it correctly. The sibling tool names further reinforce when this tool is appropriate. Nothing essential for invocation is missing.

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?

The schema provides only a title and type for file_path, with 0% description coverage. The description compensates by stating 'Path to the .excalidraw file,' clarifying that the parameter is a filesystem path to an Excalidraw file. This is minimal but sufficient for a single-parameter tool.

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 opens with a specific verb-resource pair: 'Read and analyze an existing .excalidraw file.' This clearly distinguishes the tool from the many create/import/modify sibling tools and defines exactly what it operates on. The listed return contents (shapes, connections, color scheme) further clarify its analytical purpose.

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 phrase 'existing .excalidraw file' provides clear context that this tool is for inspecting already-created diagram files, separating it from creation and modification siblings. However, it does not explicitly state when not to use it or name alternative tools.

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