crm_enrich_leads

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

The description mentions routing under JWT, tenant, and company scope, adding minimal authentication context. However, it does not disclose whether the tool is read-only, modifies data, or has other behavioral traits. With no annotations, the description carries the full burden but fails to provide sufficient transparency.

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 very short and front-loaded with the action name, but it sacrifices clarity for brevity. The structure is acceptable but lacks meaningful content per sentence.

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?

Despite an output schema being present, the description does not mention return values or side effects. The tool's purpose ('enrich leads') remains undefined, leaving the agent without a complete understanding of what the tool does or yields.

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 0%, so the description must compensate. It only reiterates the schema's field names ('free-text objective', 'optional JSON string') without adding syntax, constraints, or examples. This adds negligible value beyond what the schema already implies.

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 'Run the crm domain agent action enrich_leads' but does not explain what enriching leads entails. It fails to distinguish from sibling tools like crm_enrich_contact or crm_verify_lead, leaving the agent uncertain about the tool's specific function.

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 is provided on when to use this tool versus alternatives. There is no clarification of prerequisites, limitations, or contextual cues for invocation.

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