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

No annotations are provided, so the description carries full behavioral burden. It does useful work by enumerating the returned payload (status, version, claimed flag, handoff link, previews), which hints at a read-only snapshot, but it discloses nothing about permissions or the id-based TTL access model that the schema mentions.

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?

A single front-loaded sentence with zero padding, and the returned-field enumeration is packed efficiently into the same line. Every clause earns its place.

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 and no annotations, the description compensates well by listing the fields returned, so an agent knows what to expect from a call. It is only slightly short of complete because it omits any note on access/TTL semantics or failure behavior.

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 designId parameter has 100% schema description coverage, including the dsg_… format and the access-granting TTL note. The description adds only 'by its designId', so the baseline of 3 applies when the schema does the heavy lifting.

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 (Fetch) and resource (a draft's current document) and even enumerates the returned fields — document, status, version, claimed flag, handoff link, previews. It is clear what the tool does, but it never distinguishes itself from siblings like get_handoff_link, render_preview, or update_design that overlap with the data it returns.

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 alternative sibling is named (e.g. why not get_handoff_link for the link, or render_preview for previews). The usage is only implied by the verb 'Fetch'.

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