getPerson

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get a single person by ID' without mentioning return format, default fields, error handling, rate limits, or any side effects. As a read operation, it does not disclose even basic expectations like whether the ID must be unique or what happens if not found.

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 a single, concise sentence with no filler. It front-loads the essential purpose and does not waste words, earning a perfect score for brevity and clarity.

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 simplicity (2 params, no output schema, no annotations), the description would benefit from mentioning that the response contains a person object and that the 'fields' parameter can customize the response. It omits any mention of return value or how to control output, so it feels incomplete for agents needing to know what to expect.

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% and both parameters are described in the input schema (id as 'Person ID', fields with detailed explanation). The description adds no extra meaning beyond what the schema already states, so it meets the baseline but does not exceed it.

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 'Get a single person by ID' uses a specific verb (Get) and resource (single person) and clearly specifies the retrieval method (by ID). This distinguishes it from siblings like getPersonByEmail (by email) and listPeople (list many), so the purpose is unambiguous.

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 implies usage when an ID is known, but it does not explicitly mention alternatives (e.g., using getPersonByEmail when only an email is available) or state when not to use it. The required 'id' parameter indicates usage context, but there is no explicit guidance.

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