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

Annotations establish that this writes (readOnlyHint=false) and reaches external sites (openWorldHint=true), and the description goes well beyond that by disclosing the exact pipeline: it reads the site licence, downloads the file, validates printability, persists a saved quote, and returns an estimate plus a private link to the stored quote. It also states the multi-file listing behavior and the rights-confirmation fallback — real behavioral context the annotations cannot convey.

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?

Front-loaded with the trigger ('Use this when...') followed by the operation sequence and then edge cases; every sentence carries information. Sentences are long and clause-heavy, which slightly hurts scanability, but there is little true redundancy.

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 complex, open-world, write-enabled tool with 7 parameters, the description covers the trigger, the multi-step behavior, the artifact created, and the out-of-scope case. Because an output schema exists, it need not explain return values, and nothing an agent needs to invoke it correctly is missing.

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 the baseline is 3. The description adds meaning on top of the schema by explaining the multi-file selection round-trip (which motivates file_key) and the condition under which rights_confirmed is required, giving workflow context the field descriptions alone don't provide.

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 ('quote ... to have it printed and shipped') and spells out the full operation: read licence, fetch file, check printability, save quote, return estimate. It clearly separates this link-driven flow from the sibling get_print_quote without naming it, so an agent can identify it precisely.

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?

"Use this when someone shares a link to a 3D model" gives an explicit trigger condition, and the closing sentence handles the when-not case (non-model links require rights confirmation). It does not name alternative sibling tools for other quoting paths (e.g. get_print_quote, update_print_quote), so it stops short of full routing guidance.

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