delete_deal_note

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Delete' without addressing permanence, side effects, authorization requirements, or what happens to related data. The description adds minimal behavioral context beyond the action itself.

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 extremely concise, with no filler words. It front-loads the action and only includes necessary parameter lines. However, the under-specification of behavioral context slightly reduces its value, but conciseness itself is good.

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 having an output schema, the description does not address key contextual aspects such as whether the deletion is permanent, potential errors, or relationships to other entities. The tool is simple but the description is too sparse to be considered complete for a mutation operation.

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 explicitly identifies deal_id as 'The Nimble deal ID' and note_id as 'The note ID,' which adds slight context beyond the schema's minimal titles. However, it does not explain formats, sources, or relationships, and with 0% schema description coverage, it only partially compensates.

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 'Delete a note from a deal,' which specifies the action (delete) and the resource (note within a deal). This distinguishes it from sibling tools like delete_note or delete_deal, though it does not explicitly call them out.

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?

No guidance is provided on when to use this tool versus alternative deletion tools (e.g., delete_note, delete_contact). There is no mention of prerequisites, such as requiring deal and note IDs ownership or permissions.

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