pipedrive_list_persons

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the description adds minimal behavioral context. It mentions filtering options but does not disclose pagination behavior, rate limits, or what happens when no filters are applied. With annotations covering safety, the description adds some value but is not rich.

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, which is concise, but it includes an inaccurate claim about filtering by first letter of name, undermining effectiveness. Conciseness is good, but accuracy is a concern.

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?

With 12 parameters and no output schema, the description is too minimal. It does not explain the various filter options, sorting, or pagination. The user cannot fully understand the tool's capabilities from the description alone, given its complexity.

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%, so parameters are documented. However, the description claims a 'first letter of name' filter, but no such parameter exists in the schema, creating a discrepancy. This misleads the agent, reducing score.

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 'List persons (contacts)' with optional filters, identifying the verb and resource. It distinguishes from other list tools by mentioning specific filters unique to persons (owner, organization, first letter of name), though it does not explicitly differentiate from sibling tools.

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 listing persons with specific filters but does not provide explicit when-not-to-use guidance or mention alternatives like pipedrive_search_persons. The guidance is implicit rather than explicit.

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