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

Annotations already declare this is a safe read-only, non-destructive, closed-world operation. The description adds useful behavioral context by noting that export options are available 'once done,' which signals a state-dependent return and connects it to render_link.

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 efficient sentence that front-loads the lookup-by-id purpose and then lists the returned information. Every clause contributes useful context without repetition.

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?

With no output schema, the description appropriately summarizes the key returned fields and the conditional export options. It does not cover error behavior such as what happens if the id is invalid or the drawing is missing, but it is otherwise sufficient for a simple read-only getter.

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?

There is one parameter with 0% schema description coverage. The description says 'by id,' which confirms drawing_id identifies the target drawing, but it does not explain the expected id format or where to obtain it.

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 identifies a retrieval operation for a single drawing by id and enumerates what it returns: status, progress, preview page, and export options. It distinguishes itself from list_drawings by specifying lookup by id, though it does not explicitly contrast with siblings like status or wait_drawing.

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: use this when you have a drawing_id and need that drawing's current state and details. However, there is no explicit guidance on when to use this versus list_drawings, status, or wait_drawing.

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