Get person details

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds important behavioral details: roles capped at 50, order not guaranteed, sfw/sfw_strict filters apply only to credit lists (not person), and filters are 'verified live'. No contradictions.

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 comprehensive but somewhat lengthy. It front-loads the main purpose and then adds necessary details. Every sentence contributes value, but could be slightly more concise without losing information.

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?

Given the tool's complexity (3 params, output schema present), the description covers all key aspects: what data is returned, limitations, id sources, filter behavior. No critical information is missing, making it fully adequate for an agent to invoke correctly.

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 100%, so baseline is 3. The description adds extra context: explains the cap reason, the filtering behavior on credit lists vs person, and the 'verified live' note. This goes beyond the schema's parameter descriptions, meriting a 4.

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 it retrieves full person details by mal_id, listing specific data (bio, staff, voiced roles). It differentiates from siblings by explaining how to obtain the id (search_people, get_character) and noting where ids are absent (get_anime_characters' voice_actors).

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 explicitly states when to use: when you have a mal_id and need person details. It provides sources for the id and notes limitations (caps, order). While it doesn't explicitly state when not to use, the context is clear given sibling tools.

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