Get person

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

Annotations already cover safety (readOnly, idempotent, non-destructive). The description adds valuable conditional behavior: contact items and identity details are only returned with include_contact_details, and bank details are never returned. This is genuine behavioral disclosure beyond the annotations.

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?

Front-loaded with the core purpose, then field inventory, then the critical include_contact_details caveat. Efficient single paragraph without waste, though the field enumeration is slightly list-like.

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?

Covers what is returned, the conditional fields, hard exclusions (bank details), and the endpoint. No output schema exists, so return details in the description are necessary and present. Missing pagination/error context but complete for a GET-by-ID 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 coverage is 100%, so baseline is 3. The description adds meaning about what include_contact_details gates (contact items, note, identity/right-to-rent/NRL), but the schema already lists these. Marginal added value.

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+resource: retrieve one person by ID, and details what is returned. Distinguishes itself from find_people implicitly by being singular-with-ID, but doesn't name the sibling alternative explicitly. Clear but no explicit sibling differentiation.

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?

Implied usage: you call this when you have a person_id. No explicit 'use X when Y' guidance, no exclusions, and find_people isn't named as the search alternative. Contextual inference is required.

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