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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds meaningful scope context ('published', 'only their public documentary records'), hinting at a privacy/filtering boundary. It does not mention pagination behavior despite page/limit parameters existing.

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 front-loaded sentence with no filler, and the resource is stated immediately. It is efficient, though almost too terse given the four undocumented parameters it could have addressed.

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?

An output schema exists, so return values need not be described, and annotations cover the read-only safety profile. The remaining gap is parameter behavior (paging, language constraint) and selection guidance versus search_people, which the description does not address.

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 description coverage is 0% across four parameters, so the schema provides bare types and bounds only. The description adds no information about what 'id' identifies, nor about page/limit/language semantics, leaving the burden unmet for a lookup tool with paging parameters.

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 clear verb+resource: reading a published person's biography and their public documentary records. It scopes the data to 'published' and 'public', which helps distinguish it from get_documentary and search_people. However, it never names an alternative to route between, so sibling differentiation is implied rather than explicit.

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?

There is no when-to-use framing and no mention of alternatives such as search_people (to find a person) or get_documentary (for a specific film). The agent must infer that this is a lookup-by-id tool from the required 'id' parameter alone.

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