create_a_deal_note

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

Annotations already indicate write operation (readOnlyHint=false) and non-idempotence (idempotentHint=false). The description adds the note about duplicate creation, but does not provide further behavioral details like side effects, permissions, or rate limits. No contradiction with annotations.

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 relatively short but contains redundancy: 'Create a deal note' appears twice, and 'creates a new record' is repeated. The structure is adequate but could be more concise by removing duplicate statements.

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 tool is simple with only two parameters and no output schema. The description adequately covers the basic functionality but lacks details like what the response looks like or any prerequisites. Given the low complexity, the description is minimally complete.

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 100%, so parameters are fully documented in the input schema. The description does not add any additional meaning or context about the parameters (e.g., 'id' is a deal ID, 'body.note.note' is the note content). Baseline score of 3 is appropriate.

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?

Description clearly states the verb 'Create' and resource 'deal note' along with HTTP method and path. However, it does not explicitly differentiate from sibling tools like 'create_a_note' (generic note creation) or 'create_an_account_note', leaving some ambiguity about when to use this specific tool.

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 mentions idempotency ('Not idempotent — calling twice may create duplicates'), which provides some guidance. However, it lacks explicit context on when to use this tool versus other note creation tools or prerequisites, such as requiring an existing deal.

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