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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), but the description adds real value beyond them: it discloses that large files are summarized rather than inlined (an output-shape caveat an agent must anticipate) and states the 'read' scope authorization requirement.

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?

Dense, front-loaded sentences: verb+resource first, then payload contents, then the summarization caveat and auth requirement. No filler text; every clause conveys information an agent needs.

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-param read tool with no output schema, the description compensates by listing the returned file's contents and disclosing the summarization fallback. Nothing critical is missing; only the relationship to sibling retrieval/export tools is unaddressed.

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?

Only one parameter (designId) at 100% schema coverage, so the schema already documents it fully; the description adds no format, source, or naming guidance for it. Baseline 3 applies when the schema carries the parameter semantics.

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 (Fetch) and resource (a design's open-format file) and enumerates what the payload contains: pages, nodes, theme, speaker notes. This differentiates it from the sibling get_design, though it never names that sibling explicitly, so the contrast is inferable rather than stated.

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?

The 'Requires the read scope' line and the summarization behavior imply when this tool applies, but there is no explicit when-to-use guidance and no routing against siblings like get_design or export_design. Usage is implied rather than directed.

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