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

Annotations already declare readOnlyHint and destructiveHint, and the description adds meaningful behavioral context: the document must be PUBLIC and the tool never returns an edit token. This goes beyond the annotations and gives an agent a clearer expectation of the tool's behavior. No contradiction with annotations found.

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 two short, front-loaded sentences with no filler. Every phrase adds meaningful constraints: 'current', 'PUBLIC', 'using its drawing UUID', and 'never returns an edit token'.

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-only tool with supportive annotations and complete schema coverage, the description is nearly sufficient. It clearly states the resource scope and a key behavioral guarantee. It does not describe the response format, but the absence of an output schema makes that less critical for a simple drawing read.

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 fully documents the single 'id' parameter with its UUID format from /draw/<uuid>. The description adds the context of 'current public document and revision using its drawing UUID', but largely restates what the schema already provides rather than adding new parameter-level details.

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 ('Read') and clearly identifies the resource: the current public document and revision identified by a drawing UUID. It also mentions the important 'never returns an edit token' behavior, which helps distinguish it from mutation tools. However, it does not explicitly differentiate itself from sibling tools like get_drawing_format or get_drawing_preview.

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 implies the tool is for read-only access to public drawings and explicitly notes that it never returns an edit token, which suggests it is not for editing workflows. However, it does not explicitly state when to use this tool versus alternatives such as get_drawing_format or set_drawing.

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