get_person

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

No annotations are provided, so the description carries the full burden. It states that the tool retrieves 'comprehensive information including all custom fields and related data,' which is useful. However, it does not mention any side effects, permissions, or error behavior.

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 well-structured with clear sections: description, Args, Returns, and Examples. It is concise, front-loaded with the purpose, and every sentence adds value.

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 1 parameter and an output schema, the description covers retrieval purpose, parameter meaning, return format, and an example. It could mention behavior when the person ID is not found, but overall it is fairly 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?

Schema coverage is 0%, but the description adds an Args section explaining 'person_id: The Pipedrive person ID', which provides meaningful context beyond the schema's minimal type and title.

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 clearly states 'Get a single person/contact by ID', using a specific verb and resource. It distinguishes from sibling tools like 'get_persons' (plural) and 'search_persons'.

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 includes an Args and Returns section, and an example showing correct usage. However, it does not explicitly state when to use this tool over alternatives like 'get_persons' or 'search_persons'.

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