pipedrive_leads_search

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

The description only mentions 'uses v2 search API', which provides minimal behavioral context. With no annotations, it fails to disclose critical details such as the read-only nature, pagination, result format, or rate limits.

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 front-loaded sentence, which is concise but lacks sufficient detail to fully inform usage. It is appropriately sized for minimal information but sacrifices completeness.

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 the tool has 8 parameters and no output schema, the description is insufficient. It does not explain return values, pagination (cursor/limit), or how parameters interact. The agent would need additional context to use the tool effectively.

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 description coverage is only 13%, and the description adds no extra meaning to any parameters. It does not explain the purpose or behavior of fields like 'fields', 'exact_match', or 'person_id', leaving the agent to rely on the sparse schema descriptions.

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 'Search leads by term', indicating the action (search) and resource (leads). It distinguishes from siblings by specifying leads, though it does not explicitly differentiate from other search tools like pipedrive_deals_search beyond the resource name.

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 (e.g., other search tools or list tools). There is no mention of prerequisites, exclusions, or context for usage.

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