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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description still adds real behavioral context beyond the annotations: results are licence-filtered, and each hit carries title, designer, thumbnail and model_link. The only wrinkle is that searching two external third-party sites sits somewhat at odds with openWorldHint=false, which is worth noting but does not mislead the agent about safety or side effects.

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 core action and scope, then the licence constraint, then the result shape, then the usage cue, then args. Every sentence adds decision-relevant information; nothing is padding.

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 two-parameter search tool with no output schema, the description covers the domain searched, the filtering rule, the fields returned, pagination size, and when to reach for it. An agent has everything needed to call it correctly and interpret the response.

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 0%, so the description must carry the load, and it does: query is explained with concrete examples ("phone stand", "cable clip") and page is documented as 10 results per page, which the bare integer schema does not convey. It could go further on query syntax (keywords vs natural language), keeping it from a 5.

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 (printable model catalogue across Printables and Thingiverse), plus the qualifying constraint that only commercially-licensable models are returned. This clearly separates it from siblings like quote_my_file, which handle the user's own files rather than a ready-made catalogue.

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 when the person wants a ready-made model printed" gives a clear positive usage context, and the commercial-licence filter implicitly tells the agent this is the catalogue path rather than the custom-quote path. It stops short of naming the alternative tool (quote_my_file) or stating exclusions explicitly, so it is clear but not fully routing-grade.

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