search_cameras

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

No annotations exist, so the description carries the full behavioral burden, and it discloses almost nothing beyond the database size. It does not explain pagination, the default for 'limit', result ordering, or what fields are returned, all of which matter for an unannotated search tool.

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?

A single sentence that front-loads the resource and scope before listing facets. Nothing is wasted and no filler is present.

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 annotations, no output schema, and 0% parameter description coverage, the definition is too thin: it omits the limit/pagination contract and any value formats for mount, format, or price tier. An agent could not construct a reliable query from this alone.

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% for 6 parameters, so the description does most of the mapping: text→query, type, mount, format, and price tier→max_price_tier are all implied. However, 'limit' is never addressed and no accepted values or semantics for the tier/mount/format strings are given, leaving real gaps.

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 (the Openfilm classic camera database) plus its scope (60 bodies) and the searchable facets. It implicitly contrasts with the singular sibling get_camera, though it never names it or search_film_stocks explicitly.

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?

No when-to-use guidance is given — nothing tells the agent to prefer this over get_camera for a specific body, or over search_film_stocks for non-camera queries. The facet list hints at search behavior but provides no exclusions or alternative routing.

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