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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description goes further by describing what each returned item contains (findings with dates and links, likely meaning, rough time frame), which is genuinely useful context beyond the 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?

Front-loads the core action ('List the current leads') and follows with payload detail and the filter hint. Slightly conversational phrasing ('what it usually means for someone selling what you sell') costs a little density but every sentence carries information.

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?

With no output schema, the description usefully compensates by describing what returned items contain, and it clarifies the filter. It omits any mention of limit behavior, ordering, or pagination, but these are minor gaps for a two-parameter list tool.

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 the baseline is 3, but the description adds meaning to the closing_soon enum value by explaining it selects leads that 'usually wind down within 30 days' – a semantic gloss the schema's brief enum description does not provide. The limit parameter is left entirely to the 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?

States a specific verb (List) and resource (current leads), and defines leads concretely as companies that 'started something you could help with.' However, it never distinguishes itself from siblings like list_suggestions or list_accounts, and the title 'List leads' diverges from the tool name list_opportunities, which could confuse selection.

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?

Offers one concrete conditional: use filter 'closing_soon' for leads that wind down within 30 days. But there is no guidance on when to prefer this over list_accounts, list_suggestions, or get_daily_brief, so the when-to-use decision is only partially supported.

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