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

Beyond the annotations it discloses the key side effect: the new profile becomes the active one and therefore reweights every later score and generated email, which is exactly the consequence an agent needs before calling. It also discloses a dedup guard ('A recent profile for the same site is not rebuilt — the upstream reports it already exists'), which the idempotentHint=false annotation alone would not reveal.

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?

Information-dense with the purpose and the activation side effect front-loaded; every clause carries an instruction an agent could get wrong. It is a single long block, though, and the 'confirm with the user' rule is buried mid-paragraph rather than surfaced, which slightly hurts scanability.

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 one-parameter tool with annotations and no output schema, the description covers purpose, prerequisites, alternatives, scoping, side effects and repeat-call behaviour. Nothing material an agent needs in order to call it correctly is missing.

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 coverage is already 100%, so the baseline is 3; the description nevertheless adds real disambiguation by stressing twice that the URL is the seller's own site rather than the prospect's, and by stating the downstream consequence of the site's copy. It does not add URL format or validation specifics, which is a minor residual gap.

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 opens with a specific verb and resource ('Build the seller's ICP profile by reading their own website') and immediately enumerates what the profile captures (offer, value prop, roles, industries, pain points, proof points, tone). It is clearly distinguished from the read-only sibling by naming list_icp_profiles as the inspection alternative.

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?

Explicit when-to-use ('onboard a new account or after a repositioning'), explicit alternative ('use list_icp_profiles to see what is already there'), an explicit precondition ('confirm with the user before running it on a website they have not named'), and an explicit negative scoping rule ('The URL is the seller's own site, never the prospect's').

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