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

The annotations already flag the tool as destructive, open-world, and idempotent, and the description adds meaningful detail beyond them: qualifying a previously unqualified lead may create a sales opportunity and notify subscribed webhook endpoints. It also clarifies that repeating the same status does not repeat those transition effects, which is important operational context.

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 three short sentences and front-loads the core action before explaining side effects. Every sentence contributes useful behavioral context without redundancy.

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 three-parameter mutation with no output schema, the description covers the most important behavioral concerns: overwrite semantics, qualification side effects, and idempotence. It does not explicitly state what happens when unqualifying a lead or whether any return value is produced, but the structured schema and annotations cover most remaining needs.

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 67%, with lead_id and agent_id documented in the schema. The description adds useful semantic meaning for the qualified boolean by explaining transition effects, but it does not document the ID parameters or provide parameter-level guidance beyond what the schema already contains.

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 states a precise verb and resource: 'Overwrite a lead's qualified status.' It clearly distinguishes this mutation from the sibling list/get tools and makes the scoped effect on the lead's qualification understandable.

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 description implies the tool is used to change a lead's qualification status, but it does not explicitly state when to use this tool versus alternatives or when not to use it. It provides useful context about transition effects, but that is more behavioral detail than usage guidance.

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