get_person

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

The description adds no behavioral context beyond the readOnlyHint annotation. It simply repeats the purpose and the parameter, without explaining response details, authorization needs, or error behavior. Since annotations already cover the read-only nature, the description provides no additional transparency value.

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 two lines with a clean 'Args:' structure. It is highly concise, with every word contributing to meaning and no redundant content.

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 get-by-ID tool with a readOnlyHint and an output schema, the description covers the purpose and parameter adequately. It lacks explicit usage alternatives, but the tool's low complexity and effective parameter documentation make it sufficiently complete.

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?

The description explicitly defines person_id as 'The numeric person ID', adding semantic meaning to the schema's bare 'integer' type. For a single parameter, this clarification is sufficient to guide correct usage.

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 details for a specific person' clearly states a read operation for a single resource. The words 'specific person' distinguish it from list_people or get_current_person, and the verb 'get' aligns with the sibling naming pattern.

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 you have a person_id and need details, but it does not explicitly state when to prefer this over list_people or get_current_person. No exclusionary or alternative guidance is provided, leaving usage to be inferred from the parameter.

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