Enrich Lead

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

Annotations indicate idempotent, non-destructive, mutable. Description adds that it updates the lead in place and returns the enriched record, aligning with annotations. Could specify behavior if domain not found, but overall sufficient.

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?

Three sentences efficiently cover purpose, behavior, and sequencing advice. No redundant information, every sentence adds value.

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 single-param tool with no output schema, the description covers input, behavior, and recommendation. Minor gap: no mention of error cases (e.g., missing domain). Still comprehensive.

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 describes lead_id as UUID from lead_ingest/lead_search. Description adds context that enrichment uses email domain, implying lead must have one. This adds value beyond schema, so above baseline of 3.

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 enriches a lead with company data using the email domain, listing specific fields. It distinguishes from siblings by advising to run before lead_score for accuracy.

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?

Provides context that enrichment uses built-in knowledge base (no external API) and recommends ordering before lead_score. Could explicitly mention when not to use or alternative tools, but current guidance is clear.

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