Get person

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-API nature are covered. The description adds that results cover people in film roles (actor, director, …), but says nothing about what detail fields are returned or error behavior for unknown IDs — acceptable given the annotation coverage, but thin.

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?

A single sentence with the resource and the identifying parameter front-loaded; nothing extraneous and nothing buried.

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?

It is a simple one-parameter read tool with clear annotations, so the core need is met. However, there is no output schema, and the description does not characterize the returned payload beyond 'details', leaving an agent to guess what fields come back.

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?

Schema coverage is 100% and the sole parameter is fully described as 'TMDb person ID'. The description only restates that; it adds no format guidance (e.g., that it is the numeric TMDb ID, not an IMDb ID), so the baseline 3 applies.

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?

States a specific verb and resource ('Get details of a person') and scopes the input to a TMDb person ID, so an agent can distinguish it from search_media or get_favorite_people. It stops short of explicitly naming which sibling to use instead, but the ID-lookup framing is clear.

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 phrase 'by TMDb person ID' implies the prerequisite (you must already have an ID rather than a name), which is the key usage condition. No explicit when-to-use/when-not, and no mention of what to do if only a name is known (presumably use a search sibling).

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