Search movies

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds useful context: it searches an external site (moviemagnet.site), requires no authentication, and returns IMDb ids. While it doesn't discuss pagination or error behavior, the added detail about return format and auth goes beyond the bare annotations.

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 two short sentences that are front-loaded with the core purpose, then provide immediate follow-up usage. Every word earns its place, with no filler or redundant repetition of the tool name or title.

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 one-parameter search tool with no output schema, this description is complete: it states the input (title), the output (IMDb ids), the destination (moviemagnet.site), and the integration with sibling tools. The annotations cover safety and open-world behavior, so nothing critical 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 already provides 100% coverage with a clear description for the single 'query' parameter, including an example. The tool description's mention of 'by title' aligns with the schema but adds no new semantic detail beyond what the parameter description already provides, so the baseline of 3 is appropriate.

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 uses a specific verb+resource combination ('Searches moviemagnet.site for movies by title') and clearly distinguishes this tool from siblings like movies_get and movies_find_torrents by stating that it returns IMDb ids to pass to those tools. This makes its role unambiguous.

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 clearly implies when to use this tool (search by title before calling movies_get or movies_find_torrents) and states that no sign-in is required. It does not explicitly list exclusions or alternative search tools, but the intended workflow is clear from the mention of downstream tools.

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