Crear lead en Perfex CRM

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

With no annotations provided, the description carries the burden. It discloses the mechanism (web-to-lead), required configuration, and return value (success true/false). This adds useful behavioral context beyond a simple creation statement, though it does not elaborate on failure modes or side effects.

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 two sentences, front-loaded with the purpose, and includes requirements and return information. Every sentence earns its place with no 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?

Given the tool's simplicity (10 params, 1 required) and no output schema, the description adequately covers purpose, mechanism, requirements, and return. It does not explain error handling or duplicate behavior, which could be useful, but is not critical for a basic create lead tool.

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 description coverage is 100%, so the schema already documents all parameters. The description adds no additional parameter-specific details beyond mentioning the web-to-lead form, which hints at mapping but does not enrich semantics.

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's function: 'Crea un lead (cliente potencial) en Perfex CRM vía el formulario web-to-lead.' This identifies the specific verb (crea), resource (lead en Perfex CRM), and method (web-to-lead). It distinguishes from siblings like create_ticket and request_quote.

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 provides clear context for when to use the tool (when creating a lead in Perfex CRM) and mentions prerequisites (PERFEX_URL and PERFEX_FORM_KEY configurados). It does not explicitly name alternatives or exclusion cases, but the context is unambiguous.

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