Get person details

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered by structured data. The description adds some context in explaining that append pulls combined vs. split credit sets, but it does not disclose what happens on an unknown id, payload size implications, or language fallback behavior.

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 sentences, front-loaded with verb and returned fields, then the append guidance. The field enumeration is slightly sprawling but every element is informative; nothing is filler.

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?

With no output schema, the description carries the burden of describing return content and does so by listing the core fields. It is complete for correct invocation, with only minor gaps (error behavior for a bad id, whether append results are nested under a key).

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 the baseline is 3. The description goes beyond the enum list by interpreting each append value semantically (combined_credits = full filmography with movies and TV together; movie_credits/tv_credits = one kind; images = photos; external_ids = the IMDb id), which resolves ambiguity the bare enum cannot.

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?

Opens with a specific verb and resource (get the record of one person) and enumerates exactly what is returned: name, biography, birth/death dates, place of birth, known department. It clearly distinguishes itself from siblings like search_titles and get_movie, which is enough for an agent to route correctly without opening a schema.

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?

Gives explicit routing for the required id ('Get the id from search_titles with media_type person') and explains the append path for extra data. It lacks an explicit 'do not use this for X, use Y instead' exclusion, but the when-to-use context is clear and actionable.

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