revert_issue_quote

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

The description adds no behavioral context beyond what annotations already provide. With readOnlyHint=false and destructiveHint=false being generic, the agent is left without knowing whether this operation changes the quote status, requires special permissions, or is reversible. No side effects or state changes are disclosed.

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 brief but under-specified. 'Revert issue a quote' is a vague fragment, not a concise summary of a fuller explanation. It fails to front-load any actionable information and wastes the opportunity to provide clarity.

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 has only one parameter and no output schema, but the description still leaves critical gaps. It does not explain the effect of reverting an issued quote, the expected outcome, or how the operation fits into the quote lifecycle. This is insufficient for an agent to confidently invoke the tool.

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%, with quote_id described as 'the id of the quote,' so the baseline of 3 applies. However, the tool description adds no additional meaning to the parameter, leaving the agent to infer that quote_id identifies the quote to be reverted. No mention of edge cases or required formats.

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 'Revert issue a quote' essentially restates the tool name without explaining what 'revert issue' actually does. It does not distinguish this tool from siblings like issue_quote, create_reissue_quote, or revert_issue_invoice. The phrasing is grammatically ambiguous and fails to specify the action taken on the quote.

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 usage guidance is provided. The description does not state when to use this tool, what conditions warrant a revert, or how it relates to alternatives such as issue_quote or create_reissue_quote. There is no mention of prerequisites, side effects, or business context.

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