get_persons

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

No annotations provided, so description carries full burden. Merely states it retrieves a list without disclosing pagination behavior, data completeness guarantees, or access scope implied by the filtering parameters.

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 brief (7 words) and front-loaded with action verb. No wasted words, though brevity comes at cost of helpfulness given the tool's complexity.

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?

Insufficient for a 5-parameter filtering/pagination tool with no output schema or annotations. Omitting mention of pagination strategy or filtering capabilities leaves significant gaps despite full schema coverage.

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 has 100% description coverage, so baseline applies. Description adds no parameter-specific context beyond what the schema already documents for the five filtering/pagination options.

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?

States basic action (get/list) and resource (persons) with source system (Pipedrive), but fails to distinguish from sibling tools like 'get_person' (singular retrieval) or 'search_persons' (full-text 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?

Provides no guidance on when to use this bulk retrieval endpoint versus singular 'get_person', summary 'get_persons_summary', or 'search_persons' alternatives.

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