APIbase

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

Adds valuable behavioral context beyond annotations: specifies the three option types returned (streaming, rental, purchase) and indicates geographic organization ('by country'). Annotations already confirm read-only/idempotent safety; description explains what the data represents.

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?

Single sentence of 12 words with zero waste. Front-loaded action verb, immediately followed by what is found, for what content type, and key scoping detail (by country). Every word earns its place.

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?

Adequate for a simple 2-parameter lookup tool. No output schema is provided, but the description clearly signals the return structure (availability options organized by country). Could mention that results require a valid TMDB ID from prior search, but not strictly necessary.

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%, documenting both 'id' and 'type' parameters fully. Description mentions 'movie or TV show' which aligns with the type parameter, but adds no syntax examples or format details beyond what the schema already provides. Baseline appropriate for high schema coverage.

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?

Excellent specific verb ('Find') paired with exact resource scope ('streaming, rental, and purchase options'). Clearly distinguishes from sibling TMDB tools like 'details' or 'search' by focusing specifically on availability/rights information.

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?

Provides implied usage through the phrase 'Where to Watch' in the title and description content, but lacks explicit guidance on when to use this versus 'tmdb.movies.details' (which may also contain some provider data) or prerequisites like needing a TMDB ID first.

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