search_studios

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

No annotations are provided, so the description carries the burden. It discloses that it returns specific data (rates, key features) and that it's free, but doesn't mention pagination, sorting, filtering logic, or read-only nature. The 'Search' implies read-only, but more explicit disclosure would be helpful.

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 compact and front-loaded with the core purpose. Each sentence adds value: the first defines the resource, the second explains the return content, the third notes cost. No wasted words.

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 search tool with 5 optional parameters and good schema coverage, the description provides sufficient context about what results include and the free access. It lacks guidance on default behavior (e.g., max_results default) but that's in the schema. Overall complete enough for a filtered search.

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 80% (4 of 5 params have descriptions). The description adds no extra parameter detail beyond what the schema already provides, and doesn't clarify relationships like AND/OR logic. Baseline 3 is appropriate since the schema handles most parameter semantics.

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 the action ('Search') and the specific resource ('CrewOne database of Taiwan studios'), making it distinct from sibling tools like search_equipment or list_photographers. Additional context (561 studios, rates, features) further clarifies 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?

While it doesn't explicitly name alternatives or exclusions, it clearly implies when to use: when searching for studios in Taiwan with specific criteria. The mention of 'Free to use' and returns of rates/features provides practical usage context.

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