deleteDeal

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not state that deletion is irreversible, whether related data (e.g., attachments) is also removed, or what error conditions may occur. The description is too terse to be informative.

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 a single short sentence with no wasted words, but it is under-specified. It does not earn its place by providing any structuring cues (e.g., bullet points, sections). It is functional but could be more helpful without being verbose.

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 simplicity of a delete operation with one parameter, the description does not need to be lengthy. However, it omits any indication of return values, success/failure behavior, or side effects. For a tool with no output schema, the description should at least mention what happens after deletion.

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 one required parameter 'id' described as 'Deal ID'. The description adds no further meaning beyond what the schema already provides. According to guidelines, baseline 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?

The description 'Delete a deal' clearly combines a verb ('Delete') with a specific resource ('deal'), distinguishing it from sibling tools like deleteDealAttachment or deleteDealCustomField. However, it lacks any additional detail about what constitutes a 'deal' in this context.

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 provides no guidance on when to use this tool versus alternatives (e.g., soft delete via an update tool or other deletion tools). There is no mention of prerequisites, such as whether the user needs specific permissions or if the deal must be in a certain state.

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