Search TMDB People

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

With no annotations, the description carries the full burden of behavioral disclosure. It only mentions that search is performed 'by name,' but omits details such as pagination behavior, language support, adult content filtering, or return format. This is insufficient for a search tool without additional context.

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 concise sentence, front-loaded with the main action. It is not verbose, but it is perhaps too terse, omitting useful context that could be added without becoming unwieldy. Still, it earns its place with no fluff.

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?

Given the tool has 4 parameters, no annotations, no output schema, and 0% schema description coverage, the description is far from complete. It does not cover pagination, language rules, adult content, or return behavior. A search tool with this level of ambiguity would leave an agent uncertain about how to invoke it effectively.

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 has 4 parameters and 0% description coverage. The description implies the 'query' parameter through 'by name,' but the other parameters (page, language, includeAdult) are not explained. The description adds minimal meaning beyond the schema's property names and insufficiently compensates for the lack of schema documentation.

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 searches people by name and enumerates the types of people (actors, directors, writers, crew). This is a specific verb+resource combination that is easy to understand, though it does not explicitly differentiate from sibling tools like tmdb_search_multi or tmdb_get_person.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or direction to other tools like tmdb_get_person for fetching details after a search. The description only states what it does, not when to use it.

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