pipedrive_persons_get

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

No annotations are provided, and the description does not disclose behavioral traits such as being read-only or idempotent. It mentions returning 'full details including resolved custom fields' but does not clarify computational side effects or authentication requirements.

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 sentence that front-loads the purpose. Every word adds value, with no redundancy or filler.

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 low schema coverage (33%) and no output schema or annotations, the description should provide more context about the optional parameters and the structure of the returned data. It only states 'full details including resolved custom fields' but does not elaborate on what is included or how to control the response.

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 only 33% (only person_id has a description). The description does not explain the 'include_fields' or 'custom_field_keys' parameters, leaving them ambiguous. It mentions 'resolved custom fields' but fails to map this to the custom_field_keys parameter or clarify its 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 clearly states the tool retrieves a single person by ID with full details including resolved custom fields. It uses a specific verb (Get) and resource (person), and distinguishes from sibling tools like pipedrive_persons_list or pipedrive_persons_search.

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?

No guidance is provided on when to use this tool versus alternatives like pipedrive_persons_list or pipedrive_persons_search. There is no context about typical use cases or exclusions.

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