pipedrive_list_archived_leads

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. Description adds only that it lists archived leads, which is already clear from the name. No additional behavioral traits beyond annotations are disclosed.

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?

Single sentence with all essential information, no wasted words. Front-loaded with the primary action and resource.

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 read-only list tool with 7 optional parameters and no output schema, the description adequately covers purpose and key filters. However, it could mention pagination behavior (start/limit) and sorting, which are not self-explanatory from the schema alone.

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 covers 100% of parameters with descriptions. The description highlights the key filter parameters (owner, person, organization), adding value by summarizing the most commonly used filters, though it omits pagination and sort details.

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?

Description states 'List archived leads from Pipedrive' with specific verb (list) and resource (archived leads), and mentions optional filters. Clearly distinguishes from similar tools like pipedrive_list_leads by specifying 'archived'.

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?

Description implies this tool is for listing archived leads, but does not explicitly state when to use it versus alternatives like pipedrive_list_leads or pipedrive_search_leads. No exclusions or usage context provided.

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