list_leads

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

Discloses that account_id auto-resolves, per_page max 250, page is 1-indexed, and returns details. No annotations exist, so description carries burden; lacks rate limits or auth notes, but acceptable for a list tool.

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?

Structured with clear first sentence, explanation, alternative, bullet-point args, and return format. No wasted words.

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?

Covers all parameters and output structure; lacks pagination iteration details but sufficient given output schema description.

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?

Adds meaning beyond schema: account_id auto-resolves, company_id filters, per_page max, page indexing. Schema coverage 0%, so description compensates well.

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?

Clearly states 'List leads (unique people)', explains what a lead is (deduplicated person record), and distinguishes from sibling tools like get_lead_timeline and list_calls.

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?

Explicitly suggests using get_lead_timeline for full history, but could provide more guidance on when to filter by account_id vs company_id or pagination usage.

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