tmdb_person

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

The description notes the tool is 'credential-free' and returns public data, implying no authentication needed and read-only behavior. However, it lacks details on error handling, rate limits, or side effects, which is significant since no annotations are provided.

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 concise sentences that front-load the purpose and return content. No wasted words.

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 tool with 2 parameters and no output schema, the description covers the main return fields and notes public data. It does not elaborate on the filmography structure or limit parameter behavior (though schema covers limits), but overall it is sufficient.

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 covers both parameters (id, limit) with descriptions. The description adds value by listing the output fields (biography, birth date, photo, filmography) and mentioning 'normalized' data, which helps the agent understand what the tool returns.

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 retrieves a TMDB person and lists the returned fields (biography, birth date, photo, filmography). The name and description differentiate it from sibling TMDB tools like tmdb_movie or tmdb_search, but it doesn't explicitly contrast them.

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 on when to use this tool vs alternatives like tmdb_search. The description does not state prerequisites (e.g., needing a person ID) or when not to use it.

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