Get TMDB Person

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It uses 'Gets' to imply a read-only operation, but it does not mention authentication requirements, rate limits, error behavior, or the format of the 'external identity' response. The agent is left uninformed about potential side effects or prerequisites.

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, focused sentence that directly states the tool's purpose. It lists multiple data fields without unnecessary elaboration, making it highly scannable and efficient. No filler words or redundant content are present.

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 get-by-ID tool with no output schema and no annotations, the description lists several key returns, offering partial completeness. However, it omits the role of the 'language' parameter, the representation of 'external identity', and any prerequisites or authentication context. The presence of many sibling tools also leaves the description only vaguely positioned among alternatives.

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 input schema has 0% description coverage for its two parameters (personId and language). The description does not mention these parameters or explain how they affect the request; it only lists output data. An agent must guess that personId is the identifier and language controls localization, but the description adds no explicit meaning.

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 that the tool gets a person's biography, known department, birthplace, profile, and external identity. This specific verb+resource combination with enumerated fields makes it distinct from sibling tools like tmdb_get_person_credits, which focuses on credit data, and tmdb_search_people, which is for searching rather than retrieving details.

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 does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. It simply describes the outputs, leaving the agent to infer usage from the field list without guidance on choosing this over tmdb_get_person_credits or tmdb_search_people.

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