Fetch Full Lead Profiles

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds meaningful behavioral context: one heavy request per lead, ~15 KB per lead vs ~240 bytes for enrichment, the need for ENABLE_PROFILE=true, and resumability where successfully fetched leads are skipped. No contradiction with 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?

The description is front-loaded with the core purpose, then uses concise paragraphs to explain the distinction from enrich_leads, the cost/configuration caveat, and resumability. Every sentence contributes either to routing the agent correctly or to understanding operational behavior.

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?

Covers the essential operational facets: heavy cost, configuration requirement, resumability, endpoint relationship, and payload size. With an output schema present and annotations for safety, nothing material is missing for an agent to select and invoke this tool correctly.

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 100%, so the schema already documents both parameters well. The description adds some context around limit being per-call and url_or_hash identifying the query, but this is largely implicit in the schema. Baseline 3 is appropriate.

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 and resource ('Fetch full profiles for a query's leads'), and explicitly distinguishes itself from the sibling enrich_leads by describing the wider projection and heavier payload. The purpose is immediately clear and not confusable with any sibling.

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 explains when to use this tool: only for leads you are about to write to, whereas enrich_leads runs across a whole list to find who is free to message. It also notes the ENABLE_PROFILE=true requirement and resumable behavior, giving clear operational usage guidance.

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