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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/non-destructive profile is covered. The description adds the useful context that created profiles drive lead scoring, but says nothing about permissions, limits, or what happens on conflicts with existing profiles.

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 short, front-loaded sentence with no filler waste. It is efficient, though the brevity borders on under-specification for the parameter complexity involved.

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 create tool with three required parameters, a nested seven-field object, no output schema, and zero schema descriptions, the description leaves the agent without enough to populate a meaningful ICP or understand the required ids. More detail is clearly needed.

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% and the description documents no parameters at all. The nested 'icp' object contains seven subfields (name, roles, exclusions, industries, painPoints, description, intentPhrases) plus projectId and siteId, none of which are explained — a serious gap for a nested-object mutation.

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 gives a specific verb and resource ('Add a customer profile') and adds the functional context that profiles are what 'leads are scored against,' which sharpens intent beyond the name. It does not distinguish itself from siblings like update_lead_icp or delete_lead_icp, so it falls 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?

There is no guidance on when to create an ICP versus updating one, no mention of prerequisites, and no reference to alternatives in the large sibling set. The agent must infer usage entirely.

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