matchLead

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

Beyond annotations (which indicate not read-only and not destructive), the description discloses: 'SIDE EFFECT: sends real emails to real members', 'Not a dry-run - emails go out immediately', and returns a standard response envelope. This adds critical behavioral context.

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 well-structured with headings and bullet points, front-loading the main action. It is slightly lengthy but each sentence adds value, especially the warnings. Minor redundancy could be trimmed but overall efficient.

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 simple tool with one parameter, the description covers the matching logic, side effects, return format, and prerequisite lead relationship. No output schema exists, but the return envelope is described. Complete given the complexity.

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 only parameter, lead_id, is described as required and must reference an existing lead created via createLead. This adds meaning beyond the schema, which only specifies type integer. The description provides necessary constraints for correct usage.

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 tool's purpose: 'Auto-match lead to members' and explains it triggers automatic matching and sends notification emails. It distinguishes from sibling tools like createLead and createLeadMatch by specifying the automatic matching and emailing behavior.

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 states when to use: after creating a lead or needing to redistribute an existing one. Also warns to confirm with user before calling on production data, and notes it's not a dry-run. This provides clear guidance on appropriate usage.

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