Remove An Existing Markup

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

The description misstates the operation by repeatedly saying it deletes Contracts instead of Markups, which is misleading. Annotations already indicate destructive behavior, but the description adds confusion rather than clarity. Idempotency is not addressed.

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 verbose with redundant phrases like 'permanently delete' and 'cannot be undone' repeated twice. Irrelevant update logic is included, making it less efficient.

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 description lacks explanation of the return value (no output schema) and confuses the resource type. It provides some context about holders but fails to clarify how parameters relate to the deletion, leaving gaps.

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?

Input schema has 100% coverage with clear descriptions. The description redundantly lists required parameters but adds no new meaning. 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?

The description clearly states it removes a markup from a holder and supports Contract and Potential Change Order tools. Despite some redundancy, the core purpose is unambiguous and distinguishes from siblings like 'add_a_new_markup' or 'delete_markups'.

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 required admin permissions and the supported tools, but does not differentiate when to use this vs the bulk delete sibling. It also includes irrelevant update conditions that do not apply to deletion, providing no strategic guidance.

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