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

The description states 'Idempotent (setting the same status twice is a no-op)', which contradicts the annotation 'idempotentHint: false'. This is a serious inconsistency. Additionally, it mentions authentication but does not disclose side effects, permission requirements, or what happens on failure.

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?

Two sentences totaling ~40 words. The first sentence is front-loaded with the core action and optional fields. The second adds idempotency and authentication. No wasted words.

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?

Given the tool has 6 parameters, 100% schema coverage, and an output schema (not shown), the description adds idempotency and auth info. However, it lacks prerequisites (e.g., lead must exist), error handling, or integration with sibling workflows. The contradiction with annotations reduces completeness.

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 100%, so the baseline is 3. The description summarizes parameters as 'optionally, a recorded reply, pitch, or notes', but this adds minimal meaning beyond the schema descriptions. It does not provide usage examples or conditional requirements.

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 clearly states the tool advances a lead through the pipeline by setting its status or pipeline stage, with optional fields. The verb 'advance' aligns with the name 'update_outreach_lead_status', and the resource is well-defined. It does not explicitly differentiate from sibling tools like 'convert_lead_to_deal', but the core purpose is distinct enough.

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 calls it 'The core pipeline-drive action' but provides no explicit guidance on when to use this tool versus alternatives like 'convert_lead_to_deal' or 'complete_sales_task'. There is no mention of context, prerequisites, or when not to use it.

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