issue_quote

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

Annotations already indicate a write operation (readOnlyHint=false) and non-idempotency. However, the description adds no behavioral context, such as whether the quote is sent to the customer, whether it can be reverted (though a sibling tool exists), or what side effects occur. It relies entirely on annotations and provides no additional transparency.

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 this is not effective conciseness—it is under-specification. 'Issue a quote' is the minimum verbiage with no informative content, similar to the 'Process' example where brevity detracts from clarity rather than enhancing it.

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?

Even though the tool is simple (one parameter, no output schema), the description fails to provide essential context about what 'issuing' entails. It does not explain the outcome, the required state of the quote, or how it relates to sibling actions like mark_as_sent or revert_issue. This is insufficient for an agent to use the tool correctly.

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 already covers the only parameter (quote_id) with a description ('the id of the quote'), achieving 100% coverage. The tool description adds no additional parameter meaning, so the 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 'Issue a quote' is a verb+noun phrase, but 'issue' is ambiguous in this business context—it could mean send, finalize, or mark as issued. It does not distinguish from sibling tools like send_quote, mark_as_sent_quote, or revert_issue_quote, leaving the agent without a clear sense of what this specific operation does.

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 alternatives. There is no mention of prerequisites, status transitions, or exclusions. The agent is left to guess when to call issue_quote compared to the many related quote-handling tools.

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