get_film

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

With no annotations, the description discloses the expected behavior: returns a full record or null if unknown. This is sufficient for a simple read operation, though it does not cover edge cases or auth requirements.

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 with no wasted words. It front-loads the verb and quickly conveys the essential purpose and return behavior.

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 tool with one parameter and an output schema, the description sufficiently covers the action, input, and output (full record or null). The presence of an output schema further clarifies the return structure.

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 description mentions 'slug' but does not explain what a film slug is or provide examples. With 0% schema description coverage, this adds minimal meaning beyond the parameter name and type.

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 explicitly states the action ('Return'), the resource ('full film record'), and the input ('one slug'), and implies it is for a single film, distinguishing it from sibling tools like list_films or search_films.

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 usage when you have a specific slug and want a single record, but does not provide explicit guidance on when not to use it or compare with alternatives like search_films for fuzzy lookups.

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