crm_create

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

Annotations already indicate readOnlyHint=false (non-read-only) and destructiveHint=false. The description adds the behavioral detail that the operation requires user confirmation, which is not present in annotations. This goes beyond the structured fields and provides actionable context for the agent.

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 exceptionally concise—two short sentences that front-load the core purpose and then state the confirmation requirement. There is zero redundancy or filler.

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?

For a creation tool with a rich schema and output schema available, the description covers the essential purpose and the confirmation requirement. It does not mention potential side effects beyond creation, but the annotations (openWorldHint=true) and schema compensate. Overall, the description is adequate for an agent to understand when and how to invoke it.

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 input schema has 100% description coverage for both parameters, including detailed examples for the 'fields' object. The tool description adds no additional parameter guidance beyond what the schema already provides, so the baseline of 3 applies.

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 a specific verb ('создать' – create) and the exact resource types (lead, deal, contact, company). This clearly distinguishes it from siblings like crm_update, crm_delete, and crm_list, which serve different operations.

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 explicitly notes that user confirmation is required, which is a key usage constraint for a mutating operation. However, it does not explicitly name alternatives or conditions for when to use this tool over crm_update or crm_create, though the purpose itself implies creation.

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