get_person

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

No annotations provided, yet description fails to disclose error behavior (e.g., 404 vs null if person not found), return value structure, or whether this is a safe read-only operation. Carries minimal burden of behavioral disclosure.

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?

Extremely concise at six words. Action is front-loaded. No redundancy. However, brevity sacrifices opportunity to provide usage context that would elevate it to a 5 without significantly impacting length.

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?

Adequate for a simple singleton fetch operation with 100% schema coverage. Missing output description (no output schema provided) and lacks behavioral safety hints that annotations would typically cover. Sufficient but minimal.

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% with 'id' fully described as 'Person ID'. Description reinforces this with 'by ID', matching the schema semantics. No additional parameter guidance needed given single, well-documented required parameter.

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?

Uses specific verb 'Get' and resource 'person', and specifies 'by ID' which implicitly distinguishes from sibling list/search operations (get_persons, search_persons). However, lacks domain context (e.g., CRM contact vs employee) and doesn't explicitly contrast with plural variants.

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?

Provides no explicit guidance on when to use this versus get_persons or search_persons. The phrase 'by ID' implies prerequisite knowledge of the identifier, but does not state this requirement explicitly or mention error conditions when ID is unknown.

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