Get movie details

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds useful behavioral context beyond annotations: 'No sign-in required' and 'from moviemagnet.site,' which indicates the data source. This is valuable context for the agent regarding auth and provenance, though it doesn't describe response format or error behavior.

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 a single sentence, front-loaded with the action ('Fetches full details'), and every word contributes meaning. It's appropriately succinct with no filler or repetition.

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 simple single-parameter read operation with annotations covering safety, the description covers the essential context: source, auth requirement, and scope (single movie by ID). It doesn't explain return values, but no output schema exists, and the tool's simplicity makes this acceptable. Sibling tools clarify domain boundaries.

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?

The schema provides a 100% description of the sole parameter (imdbId: 'IMDb id, e.g. tt0083658'), so the description doesn't need to add parameter details. The tool description reinforces 'by IMDb id' but adds no new semantics beyond the schema, which matches the baseline 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?

The description clearly states the tool's purpose: 'Fetches full details for a single movie by IMDb id.' It specifies the resource (movie), the operation (fetch), and the identifier (IMDb id), which distinguishes it from sibling tools like movies_search (search across movies) and movies_popular (list popular movies).

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 implies when to use it: when you have a known IMDb ID and need details for a single movie. It also notes 'No sign-in required,' indicating no authentication is needed. However, it does not explicitly mention alternatives or exclusions, such as recommending movies_search when you don't have an ID, so it falls short of the highest bar.

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