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

With no annotations, the description carries the full behavioral burden. It usefully discloses that quotes and invoices already using the rate keep it, which is important non-obvious behavior, but it omits permissions, reversibility, and what happens if the rate is already archived.

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 two short sentences, front-loads the action, and immediately adds the key consequence for existing quotes and invoices. Every sentence earns its place.

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?

For a simple one-parameter archive operation, the description covers the core effect and historical preservation. However, with no annotations, no output schema, and no parameter descriptions, it leaves gaps around reversibility and how to identify the tax rate.

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 schema has 0% description coverage and the description does not explain the required tax_rate_id parameter, such as where to obtain the UUID or whether it refers to an owner or office rate. The single parameter name is self-explanatory, but usage context is missing.

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 states a specific verb and resource: "Stop using a tax rate," which clearly identifies an archive/deactivation operation. It is distinguishable from siblings like taxes_listRates, taxes_salesReport, and taxes_saveRate, though it does not explicitly name those alternatives.

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 phrase "Stop using a tax rate" implies when to use the tool, but there is no explicit when-not guidance or mention of alternatives such as using taxes_saveRate to reactivate or edit a rate. The historical-document note gives useful context but not selection guidance.

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