Add Thumbnail

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

Annotations provide only readOnlyHint=false, openWorldHint=false, destructiveHint=false, so the description carries the burden. It discloses that the thumbnail is a vector line drawing, is pinned to the corner, is left put by fit_page, is never dimensioned or counted by the manufacturability gate, and returns a soft failure rather than overlapping content. This is rich behavioral context beyond annotations.

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?

Every sentence adds distinctive information: purpose, technical rendering path, placement/pinning behavior, failure mode, and call timing. It is dense but not padded, and front-loads the core action.

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?

The description covers rendering, placement, failure behavior, timing, and return values, which is strong. However, with 0% schema parameter coverage and no output schema, the lack of any parameter semantics leaves a notable gap for an agent to formulate correct arguments.

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 schema has two parameters with zero description coverage, and the description does not explain what 'page' or 'name' refer to. The only hint is the default 'IsoThumb' in the schema. An agent would not know what value to pass for 'name' or what format 'page' expects.

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 ('Place a small isometric pictorial of the part in the top-right corner of the sheet') and clearly identifies the resource and location. It also distinguishes itself from related drawing tools by emphasizing it is a vector TechDraw projection pinned to the corner, separate from fit_page behavior.

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?

Explicitly instructs to call AFTER placing views, dimensions, and fit_page, so 'fits' is judged against the final layout. It also explains the best-effort soft-failure behavior when the corner is occupied. It does not name sibling alternatives for when not to use, but the placement timing is concrete.

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