movies_now_showing

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

With no annotations, the description carries the behavioral disclosure burden. It provides useful behavioral details: results are ordered by number of showtimes in the MovieGlu database, and the operation is a listing that returns film IDs. It does not mention rate limits or authentication, but these are not critical for this simple read-only listing tool.

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?

Each sentence earns its place: the main purpose, ordering behavior, film_id guidance, and parameter semantics are all covered in a compact, well-structured format. The description avoids fluff and front-loads the most important information.

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 single-parameter list tool with an output schema available, the description provides enough context to invoke it correctly: what it lists, how results are ordered, what the limit parameter means, and how to use the returned film_id. Nothing essential is missing.

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 only the parameter name, type, and default, with 0% schema description coverage. The description compensates fully by explaining that limit controls 'how many films to return' and adds the important max constraint of 25, which is not present in 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 begins with a specific verb and resource: 'List the top films currently in cinemas in the configured territory.' It clearly distinguishes this tool from siblings like movies_coming_soon by emphasizing 'currently in cinemas' and 'top 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 gives clear context ('currently in cinemas', 'configured territory') and tells the agent how to use the resulting film_id with related tools. It does not explicitly name exclusions or alternatives such as movies_coming_soon, but the context is strong enough to guide selection among the siblings.

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