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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the guide's content spans choosing the object, parts, camera and depth, lines, card and motion, kit and review, which is content framing rather than behavioral disclosure. It does not mention rate limits, token costs beyond the schema, or response format.

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?

Purpose is front-loaded in the first clause with the invocation hint last, and there is no filler. The mid-sentence enumeration of guide sections is a long run-on list that could be trimmed, keeping it just short of a 5.

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 zero-required-parameter retrieval tool with full schema coverage and annotations covering the safety profile, the description supplies the domain scope, the section list that stands in for return content, and the topic/query/index invocation modes. It does not address the maxTokens parameter or output size, which is a minor gap.

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 coverage is 100%, so baseline is 3, but the description adds genuine meaning by stating the fallback behavior: passing nothing returns the index of topics. That mode/selection logic is not derivable from the schema itself, so it earns above 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 states a specific verb and resource ('Returns Better Design's guide for ... isometric drawing of a small machine') and enumerates the guide's sections, which clearly separates it from its many get-*-guide siblings such as get-motion-guide or get-jig-guide. It does not explicitly name a sibling to contrast with, so it falls just short of a 5.

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 invocation guidance by naming the three modes ('Pass `topic`, `query`, or nothing for the index of topics'), which tells the agent how to call it. It says nothing about when to prefer this guide over e.g. review-illustration or get-inspiration, so there is no when/when-not routing.

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