create_a_deal_new

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

Annotations already indicate non-read-only, non-idempotent, and non-destructive behavior. The description adds 'Not idempotent — calling twice may create duplicates,' which aligns and adds slight context, but no additional behaviors (e.g., auth, rate limits) are disclosed.

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 repetitive ('Create a deal' appears twice, plus 'Creates a new record'). While it includes a useful first line with emoji and method, it could be more concise and front-loaded.

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 complex nested schema and no output schema, the description is too minimal. It lacks information on prerequisites, expected response, or when to use this tool over others. Annotations provide basic hints but the description does not compensate for the tool's complexity.

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% coverage with detailed descriptions for all parameters. The description does not add any parameter-level information beyond what the schema provides, meeting the baseline for high coverage.

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 deal' and 'Creates a new record.' It includes the HTTP method and endpoint, and the title from annotations reinforces the purpose. The tool name and description distinguish it from sibling tools like create_a_deal_note or update_a_deal_new.

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 this tool is for creating a new deal but provides no explicit guidance on when to use it vs alternatives (e.g., update_a_deal_new). It mentions idempotency but does not specify prerequisites or context for usage.

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