search_idle_leads

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

No annotations are provided, so the description carries the full burden. It discloses the behavioral nuance of using both updatedAt and latestActivityCreatedAt, enforcing that both must be before the threshold. It also mentions pagination defaults. Missing are any authentication needs or error behavior, but the core behavior is well explained.

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 concise—just a few sentences—with no wasted words. It front-loads the purpose and then efficiently explains the dual-date logic and each parameter. Every sentence earns its place.

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 search tool with an output schema, the description covers all parameters, explains the selection logic, and provides defaults. It is complete enough for an agent to correctly invoke the tool without additional context.

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 0%, so the description must compensate. It provides meaning for all parameters: days with usage example, time_zone with default and example, page with '0-based', size with max 100 and default, and sort with default value. This adds significant value beyond the bare schema.

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 verb 'Search' and the resource 'idle/stagnant leads'. It explains the precise logic using both updatedAt and latestActivityCreatedAt. This distinguishes it from sibling tools like search_leads and search_leads_by_term which search by other criteria.

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 explicitly says 'Search for idle/stagnant leads: no activity for at least the given number of days', providing clear when-to-use context. It explains the dual-date condition but does not explicitly state when not to use or mention alternatives. However, the context is sufficient for an agent to understand when to select this tool over siblings.

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