justwatch_search

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

No annotations are provided, so the description must carry full behavioral burden. It states the use of a public credential-free website, implying no authentication. But it does not mention rate limits, whether the operation is read-only, or what data is returned. This is insufficient for a fully transparent description.

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 at two sentences. The first sentence front-loads the purpose, the second adds context on the endpoint and parameter formatting. No superfluous content.

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 4 parameters and no output schema, the description adequately covers the endpoint source and parameter constraints. However, it lacks information on result format, pagination, or error handling. For a simple search, it is minimally complete.

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 100%, so the schema already documents all parameters. The description adds formatting details for country and language (e.g., 'US', 'en') but these are minor. For limit, the schema already notes defaults and clamping. Thus the description adds only marginal value beyond the schema.

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 tool searches JustWatch titles using a public GraphQL endpoint. The verb 'search' and resource 'JustWatch titles' are specific. However, it does not differentiate from sibling tools like justwatch_discover or justwatch_popular which also return titles but via different criteria.

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 format requirements for country and language parameters ('two-letter ISO code', 'two-letter code'). It also mentions the endpoint is credential-free. However, it does not explicitly state when to use this search tool versus alternative title-finding tools like justwatch_discover or justwatch_popular.

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