Search people

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds value by specifying the output includes the TMDB id and best-known titles, and that the id is needed by get_person. However, it does not disclose ordering, pagination limits, or rate limiting, but these are less critical given the read-only, open-world nature.

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?

Single sentence, front-loaded with action and resource, followed by a clear outcome. No redundant information; every word serves a purpose. Exceptionally concise for the information conveyed.

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?

Tool is simple with 4 parameters and no output schema. Description explains the primary purpose and the returned items (id and titles), but lacks detail on the response structure (e.g., list of results, pagination field). Adequate for basic use but leaves some ambiguity for an agent needing precise formatting.

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?

Input schema has 100% description coverage for all 4 parameters. The description does not add extra meaning beyond the schema (e.g., 'by name' matches query param). Baseline 3 is appropriate as schema already thoroughly documents each parameter.

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?

Description clearly states verb 'Search', resource 'TMDB people' (specified as actors, directors, crew), and method 'by name'. It distinguishes from sibling search tools like search_movies by focusing on people and mentions the returned TMDB id used by get_person, making the purpose 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?

Implicitly indicates use when you need a person's TMDB id for get_person, but does not explicitly state when to use vs alternatives like search_movies or search_multi. No direct comparison or exclusion guidance, leaving the agent to infer from the name and description alone.

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