list_leads

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint, so the description does not need to repeat safety info. It adds value by disclosing that results are sorted by modification date (newest first) and that funnel names are accepted as input. No contradictions with annotations.

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?

Two sentences: first clearly states the core action and resources, second adds sorting and filter info. Front-loaded with purpose, no wasted words. Ideal for quick agent comprehension.

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?

Description covers all essential aspects: what the tool does, required parameter with lookup options, sorting order, and available filters. Pagination (limit) is documented in schema; output schema exists for return values. No gaps given the tool's simplicity and sibling 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 coverage is 100%, so baseline is 3. The description adds meaning by explaining the funnel parameter can be an ID (from list_funnels) or a name, and by summarizing filter capabilities (status, assignee, title search) that correspond to schema properties. This goes beyond the schema alone.

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 clearly states the tool queries leads in a funnel, mentioning the required funnel parameter and optional filters. It distinguishes from siblings like list_funnels (which lists funnels) and other list tools by specifying the resource and context.

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 explains how to obtain the funnel ID from list_funnels and allows using a funnel name for convenience. It lists supported filters (status, assignee, title search) but does not explicitly state when not to use this tool or mention alternatives. The guidance is clear but incomplete.

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