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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description focuses on value-add: license filtering on Printables and pre-scaling on Poly Haven results. It doesn't mention result limits or ranking behavior, keeping it below a 5.

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?

One compact sentence plus a return-value clause, front-loaded with the action. Minor typo ('ply may print') and the parenthetical license note brush up against density, but nothing is wasted.

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?

With no output schema, the description explicitly enumerates returned fields (titles, designers, licenses, page links), which is exactly what an agent needs to use results. Sources and filtering semantics are also covered.

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?

Single parameter with 100% schema coverage including an example, so the schema does the work. The description adds nothing about query syntax or matching behavior, so the baseline of 3 applies.

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 (Search) and resource (ready-made 3D models) and names the two sources (Printables, Poly Haven). It also states an exclusion (non-commercial models left out), which sharply separates it from siblings like make_part or list_materials.

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?

Makes the selection condition clear: use this when you need ready-made models you may print and sell, with commercial licensing enforced. It does not name a sibling tool as an alternative, which is the only missing piece.

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