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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the agent knows this is a non-idempotent write that touches external systems. The description adds nothing beyond that: no note on duplicates, failure modes, required permissions, or what the response contains (e.g., new lead ID).

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity contributes to the missing information elsewhere rather than being a pure strength.

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 12-parameter mutation with no output schema and no documentation of any field, the description is far too thin. It should at minimum state that all fields are optional, how the default stage behaves, and what happens on duplicate or invalid input; none of that is covered.

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?

With 12 parameters at 0% schema description coverage and zero required fields, the description is the only place to explain that every field is optional, that first_name/last_name/email are the meaningful identity fields, or what the stage enum values mean. Instead it only says "contact details and a pipeline stage," which merely restates parameter names without adding format, default, or validation meaning.

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 specific verb and resource ("Adds a sales lead") and mentions the two main content areas (contact details, pipeline stage), so the purpose is unambiguous. It does not distinguish itself from sibling creation tools such as create_contact or create_opportunity, leaving the agent to infer which entity type this creates.

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 use create_lead versus create_contact or create_opportunity, and no prerequisites or follow-up steps are mentioned. The agent must infer usage purely from the name.

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