movie_matcher

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

No annotations are provided, so the description carries the full burden. The verb "get" implies a read-only lookup and the intent sentence adds locating context, but nothing is said about title matching behavior (exact vs. fuzzy), what happens when the title is unknown, or how large the returned scene set may be.

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?

Two short sentences, front-loaded with the action and followed by the intent. The phrase "uses the movie title to" is slightly wordy but nothing here is filler or redundant.

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?

The tool is simple: one required string parameter and an existing output schema that documents the returned scene summaries. Given that return values are covered elsewhere and the operation is a trivial read, the description supplies enough for correct invocation, with only matching semantics as a residual gap.

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?

There is one parameter with 0% schema description coverage, so the description must compensate. It does establish that movie_title is the lookup key for retrieval, but it adds no constraints on format, casing, or matching tolerance beyond the parameter name itself.

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?

States a concrete verb-plus-resource: retrieves all scene summaries for a given movie title. The purpose is intelligible without opening the schema, but it never acknowledges the sibling tool summary_to_full, so an agent cannot distinguish the two from the description alone.

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?

"Use to find where the user is in the movie" supplies one contextual use case, which is helpful but only implied guidance. There are no exclusion conditions, no mention of when summary_to_full would be preferable, and no prerequisites such as the title needing to match a known film.

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