Convert a lead to a company

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

The description details side effects: field mappings, lead state change, and error on duplicate conversion. Annotations only provide readOnlyHint and destructiveHint as false, so the description adds valuable context.

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 concise sentences that front-load the core function and then add side effects. Every sentence adds value 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?

The description explains the conversion process, field mapping, optional contact creation, and error condition. With no output schema, mentioning the return value would improve completeness, but it is adequate.

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 75%, and the description adds meaning to parameters like companyName and createContact. However, the project parameter lacks description in both schema and description.

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 that the tool converts a qualified lead into a CRM company with specific field mappings and side effects. It distinguishes itself from sibling tools like enrich_lead and set_lead_status.

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 implies the lead should be qualified and warns about errors if already converted, but does not explicitly guide when to use this tool versus alternatives like add_company or enrich_lead.

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