create_deal

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

Annotations already indicate readOnlyHint=false (mutation) and destructiveHint=false. The description adds that it creates a new deal, which is consistent but adds no additional behavioral traits like side effects, rate limits, or error conditions beyond the basic operation.

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 three succinct sentences with no wasted words. It front-loads the main purpose and provides essential usage guidance efficiently.

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 the complexity of 10 parameters and zero schema coverage, the description only covers 2 parameters (origin_id and fields). It omits mention of other optional parameters like stage_id, user_id, etc., leaving the agent underinformed. An output schema exists, which explains return values, but parameter coverage is insufficient.

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 description explains origin_id (required) and fields (custom JSON object), but ignores 8 other parameters (name, phone, email, etc.). With 0% schema description coverage, the description should compensate by covering more parameters, but it does not. This leaves many parameters undocumented.

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 'Create a new deal in the CRM,' which is a specific verb and resource. It distinguishes from sibling create tools like create_contact by explicitly naming the resource. It also provides context about required origin_id and custom fields.

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 advises using list_origins to find valid origin IDs and list_fields to discover field keys, offering clear prerequisites. However, it does not explicitly state when not to use this tool versus alternatives like update_deal, but the context is sufficient for a create operation.

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