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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: a 'realistic' request can't actually render materials here and returns a CAD image plus an explanatory note, which sets correct caller expectations.

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?

Single tight paragraph, front-loaded with the action and return value, then parameter detail. The parenthetical about PartForge's lack of a live browser is slightly long but earns its place by explaining the fallback.

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 read-only render tool whose annotations cover safety and whose output is images rather than structured data, the definition is nearly complete: it explains what is returned, the angle options, and the appearance fallback. Lacks only an explicit steer on sibling alternatives.

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?

With only 33% schema description coverage, the description carries the load for `views` and `appearance`. It adds genuinely useful detail the schema lacks: the default view set (iso, front, top) and the default appearance (cad). The max-6 constraint is redundant with the schema but harmless.

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+resource: render a forge's saved tree from canonical camera angles and return images. Clear enough to distinguish from sibling rendering/viewer tools like show_forge or viewer_load_forge without opening either schema.

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 invocation-relevant context (default views, max 6, appearance options, fallback behavior) but never explicitly says when to choose this over sibling tools such as show_forge or viewer_load_forge. Usage is implied rather than stated.

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