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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description states 'remove', which aligns with destructive, but adds no extra behavioral context (e.g., permanence, cascading effects, or the need for confirmation). Since annotations carry the safety profile, this is a minimal but acceptable disclosure.

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, direct sentence with no wasted words. It front-loads the action and object clearly. This is concise and well-structured.

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 simplicity, the description is adequate. The annotations cover destructive and idempotent hints, and the schema documents all parameters including the confirmation requirement. However, it lacks any warning about the irreversible nature or any expected outcome, which would be helpful for a destructive operation. Still, the essential information is present.

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 description coverage is 100%, and each parameter has a description (job_id: 'Job id', event_id: 'Negotiation event id', confirmed: 'Must be true after the user confirms deletion'). The tool description adds no additional parameter meaning beyond what the schema already provides, so it meets the baseline without enhancement.

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 'Remove a negotiation event from an offer' specifies a clear verb (remove) and specific resource (negotiation event within an offer). It effectively distinguishes from sibling tools like jobs.offer.delete (which deletes the offer itself) by targeting a sub-resource. The meaning is unambiguous and immediately actionable.

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 regarding when to use this tool versus alternatives. There is no mention of prerequisites, such as confirmation flow (despite the confirmed parameter), or any distinction from jobs.offer.delete. The description only states what it does, not when or why an agent should choose it.

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