search_models

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

The description discloses pagination parameters (page, per_page with default and max), sort options, and the return format (list of model summaries with specific fields). It lacks mention of rate limits or authentication, but for a search tool with no annotations, this is adequate.

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 description is concise: one sentence for purpose, a structured argument list, and a one-sentence return description. It is front-loaded and efficient, though slightly verbose with the Args: formatting.

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?

Given the tool is a simple search with 4 parameters and no output schema, the description covers the purpose, parameters, and return format adequately. It also provides related tools for deeper inspection. It is sufficiently complete for an AI agent to use correctly.

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%, so the description carries full burden. It explains all four parameters: query (keywords with examples), page (1-based), per_page (default 10, max 100), sort (four allowed values). This adds significant meaning beyond the bare schema, enabling correct use.

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 clearly states it searches Thingiverse for 3D-printable models with a specific verb (Search) and resource (Thingiverse 3D-printable models). It distinguishes itself by referencing sister tools (model_details, model_files) for next steps, and context from sibling names (like search_all_models) implies a focused scope.

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?

The description provides clear context: use for searching Thingiverse models, and then use model_details or model_files for further details. It does not explicitly exclude alternatives like browse_models or search_all_models, but the guidance is clear enough.

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