get_people_by_id

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so the safety bar is covered. The description adds a modest behavioral fact — id accepts a slug as well as an id — but does not mention 404 behavior or how a non-null extended value reshapes the response. Output schema covers return structure.

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?

Three compact units — one-sentence purpose, endpoint, and a two-line arg list. The core function is front-loaded and the structure is scannable, with zero 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?

For a simple read-only single-resource fetch with comprehensive annotations and an existing output schema, this is largely complete. The main gap is under-specified valid values for extended; otherwise an agent has what it needs to call the tool.

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%, so the description must carry parameter meaning. The id line adds real value ('The id/slug of the resource'). The extended line ('Extended information to include in the response') is near-tautological and gives no valid value hints, so an agent cannot construct an informed value. Partial compensation only.

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 a single person') plus the HTTP endpoint (GET /people/{id}/). 'Person' is distinct from 'user' in this API, and the singular scope separates it from siblings like get_people_by_id_movies, get_people_by_id_shows, and get_people_by_id_lists_by_type_by_sort. An agent can tell exactly what it does.

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?

No guidance on when to use this tool versus alternatives. It does not mention that a person's filmography is available via get_people_by_id_movies/get_people_by_id_shows, or when the extended parameter is warranted. Usage is only implied by the name and endpoint, never stated.

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