crm_verify_lead

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

The description provides minimal insight into side effects or behavior. It mentions scoping (JWT, tenant, company) but not what the action actually does. The destructiveHint annotation is present but the description adds little beyond that.

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 concise, with a clear structure: action statement, context, and parameter descriptions. No unnecessary 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?

The tool is part of a large set of CRM/domain tools, but the description lacks enough context to understand its role. It doesn't explain the purpose of verifying a lead or how it fits into workflows, leaving the agent uncertain.

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?

The schema has no descriptions for parameters, and while the description provides one-line explanations (free-text objective, optional JSON string), they are too vague to understand what content should be provided. Partial compensation for the 0% schema coverage.

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 runs the 'verify_lead' domain agent action, providing a specific verb and resource. It distinguishes from siblings by naming the action, though it doesn't explain what verifying a lead entails.

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?

No guidance on when to use this tool vs alternatives. The description only mentions routing through the dispatcher, not specific scenarios or conditions. No comparison to other CRM tools.

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