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

The description adds substantial context: it specifies the underlying GET URL, explains the 32x32 PNG thumbnail and 404 behaviors for Undrawn/Refused/missing/withdrawn/moderation-hidden cases, lists state distinctions, and describes focus mode returning an outline unless show_everything is set. Annotations already mark it readOnly/idempotent and non-destructive, so the bar is lower, but the description provides substantial additional behavioral detail about response shape, auth-free public read, and focus mode, warranting a 4.

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 dense wall of clauses covering URL, thumbnail, 404s, states, response payload, focus mode, and a front_door pointer. It's front-loaded with the core purpose, but it crams many distinct concerns into one paragraph with little structural separation, making it harder to scan than necessary.

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 readonly drawing-read tool with no output schema and partial schema coverage, the description covers response shape (palette, indices, rows) and focus-mode variations well. However, it doesn't clarify the parameter semantics for 'type' vs the 'source' values it mentions, and it omits return-value structure details an agent might need since no output schema exists. It's adequate but has gaps.

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 description coverage is only 33%, so the description does some compensating: it implies type values 'none, resident, place, thing, kind_base, or kind_variant' for the source, which is somewhat misaligned with the enum {place, resident, kind, thing}, but it does explain show_everything's effect (sending bodies this once, no effect while focus mode off). The id parameter remains undocumented beyond the schema. It adds meaningful semantic context for show_everything and the type/id usage, good value over the schema.

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 states a specific verb (read/deliberately read) and a specific resource (one current public place, resident, kind, or thing drawing), and the title reinforces it. It doesn't explicitly differentiate from sibling drawing_history or draw_self, which also concern drawings, but the 'one current' framing and the scope of object types give an agent enough to tell it apart.

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?

It gives a clear context: read the drawing of a specific record type/id, with an explicit note that ordinary map, place, window, and census reads don't carry this payload, implying to use this tool when you need the drawing specifically. It doesn't name when to use drawing_history or draw_self instead, but it does reference front_door for help, giving clear usage context without full exclusions.

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