add_thumbnail

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It discloses that the thumbnail is rendered through the same vector path as other views, scaled to a reserved top-right box, pinned there, left untouched by fit_page, excluded from dimensioning and the manufacturability gate, and returned as a structured best-effort result with placed/box/scale/view/reason fields.

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?

The core action is front-loaded and the structure moves logically from placement to rendering behavior to failure handling to return shape. It is somewhat verbose and repeats the fit/overlap condition, but the length is mostly justified by the tool's behavioral complexity.

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 tool with no annotations and no output schema, the description is quite complete: it explains placement, rendering type, fit_page interaction, manufacturability-gate exclusion, failure mode, and return fields. The notable gap is parameter meaning for page and name, which is left entirely to the undocumented schema.

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 description coverage is 0% for two parameters, and the description never explains the page or name parameters. It refers generically to "the sheet" but does not say what page accepts or what name controls, leaving the agent with no semantic guidance beyond the raw schema.

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: place a small isometric pictorial of the part in the top-right corner of the sheet. It immediately distinguishes the output from other drawing content by describing it as a vector-line isometric TechDraw projection, not a raster, and as the machinist's glance reference.

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 explicit timing and conditions: call AFTER placing views and dimensions and after fit_page, so "fits" is judged against the final layout. It also states the when-not case clearly: if the top-right corner is already occupied, it returns placed=False rather than overlapping content.

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