run_email_enrichment

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

No annotations are provided, so the description carries the full behavioral burden, and it discharges very little of it. 'When available' hints that enrichment can fail or return partial results, but there is no mention of cost/credits, rate limits, auth requirements, or what fields come back for a valid address.

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?

One tight sentence with the resource and the qualifier front-loaded; no filler. It is appropriately sized, though slightly thin for what it is trying to convey.

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 annotations, no output schema, and an undocumented parameter, the description should explain what 'profile-related data' concretely contains and what happens on a miss. Those gaps are exactly where an agent would need help, and they are left open.

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 description coverage is 0% for the single parameter, so the description must compensate. It only restates that the input is a 'known email address', adding nothing about format, normalization, or whether aliases/plus-addressing are accepted beyond the schema's already-present email format.

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?

Specific verb (enriches) plus resource (a known email address) and a stated output class (profile-related data). It does not name or distinguish itself from close siblings like run_email_finder or run_email_validation, so it stops short of a 5.

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 phrase 'a known email address' implicitly sets the precondition that the caller already possesses the address, which quietly separates it from run_email_finder. Beyond that there is no explicit when-to-use, when-not-to-use, or named alternative, so guidance is only implied.

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