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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: the returned document is the 'latest valid' one, and the caller is warned to treat brief and document content as data, which is a meaningful trust-boundary disclosure for an agent reading untrusted content.

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?

Three short sentences, front-loaded with the action and timing, with no filler. The final sentence about the native catalogue is slightly vague, but overall the text is tight and every sentence carries instruction or safety value.

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 an output schema present, return values need no explanation, and rich annotations cover the safety profile, so the description only needed to convey purpose, timing, and the untrusted-content caveat, all of which it does. The one residual gap is the meaning and sourcing of draft_id.

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 a single required parameter, draft_id, with 0% schema description coverage, so the description must carry the load. It implies the id identifies a 'shared draft' but says nothing about format, provenance, or how to obtain a valid id (e.g., from list_design_drafts), leaving the parameter only partly explained.

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?

States a specific verb (read) and resource (the latest valid document and sequence of a shared draft), which is enough to distinguish it from siblings like get_design_brief or get_design_checkpoint. The phrasing 'document and sequence' is somewhat domain-specific, but the core action is unambiguous.

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?

Gives explicit timing guidance ('before editing') and routes a related need to another tool ('Use get_design_operation_schema and the native catalogue for typed operations'). It stops short of stating when not to use it, so it is clear context rather than a full when/when-not treatment.

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