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 transparently discloses the beta state, manual onboarding ('emails Spencer'), and that leads are created and approved before posting. It could be improved by mentioning error handling or cancellation process.

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, with three sentences that front-load the purpose and then provide behavioral context and caveats. No redundant or unnecessary 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?

Given no output schema and no annotations, the description adequately sets expectations: continuous feed, webhook delivery, budget cap, beta state, manual setup. Missing details on how to cancel or what the POST payload includes (partially in schema but not in description) prevent a perfect score.

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?

The schema covers 67% of parameters with descriptions (webhook_url and monthly_lead_budget). The description adds context by explaining that monthly_lead_budget caps leads pushed. However, the filter parameter lacks details on its sub-properties (state, min_score, signal_types) beyond being mentioned as 'matching a filter.'

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 action ('subscribe') and the resource ('continuous feed of new seller-signal leads matching a filter'). It distinguishes from sibling tools like search_leads (one-time query) and purchase_lead (single lead) by emphasizing continuous delivery via webhook.

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 'Ideal for AI agents that act on leads automatically,' providing clear context for use. It also notes the beta status and manual provisioning, which sets expectations. However, it does not explicitly state when not to use or mention alternatives.

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