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

Annotations already establish this as a safe, idempotent, closed-world read, so the description's job is to disclose the return shape, and it does: solids, objects with sizes and positions, hand-drawn flat shapes, and script text with line numbers. That is meaningful added context given there is no output schema. It stops short of noting ordering, units/coordinate conventions, or behavior when the drawing is empty.

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?

One dense sentence with the subject front-loaded and each clause carrying a distinct fact about the result. No filler or redundant restatement of the title.

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 single-parameter read tool with full annotation coverage and no output schema, enumerating the result categories is close to sufficient. Minor gaps remain: no statement about what happens when the id is unknown or the drawing is empty, and no hint about ordering or units for the reported sizes and places.

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 single parameter is fully documented in the schema at 100% coverage, including the default fallback to the last-worked drawing. The description adds nothing about the parameter, which is acceptable at this coverage level but earns only 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 names the resource (a drawing's current contents) and enumerates what is returned: solids and objects with sizes and places, hand-drawn flat shapes, and the script with line numbers. The verb is implicit ('what is in a drawing now' means inspect/read state), so it is not as crisp as an explicit 'read/inspect' verb, but the content is specific enough to distinguish this from list-type siblings like drawings.

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?

There is no when-to-use or when-not-to-use guidance and no routing to alternatives; the closest candidates, view and drawings, are never mentioned. The word 'now' faintly implies a current-state snapshot rather than history, but an agent must guess which sibling to pick for visual or listing needs.

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