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

Annotations already include destructiveHint=true and readOnlyHint=false, so the description's explicit mention of 'destructive rule-removal path' reinforces this. The additional advice to 'preview its impact first' adds useful context beyond annotations, such as the suggestion to check consequences before executing.

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 sentence that front-loads the action and target, and adds a cautionary note. It is concise without redundancies, though it could be even more compact.

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 that this is a destructive operation with no output schema and only three parameters, the description covers the action, target, and a cautionary note. However, it does not clarify the meaning of portfolioRef or workspaceRef, which might be critical for correct invocation. The complexity is low, but the lack of parameter semantics slightly reduces completeness.

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, so the description must compensate. It mentions ruleRef as the target but does not clarify the role of workspaceRef and portfolioRef beyond being required contexts. This is a gap, but with three parameters all having minLength constraints, the description at least identifies the main identifier.

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 the verb 'Remove' and the resource 'saved accounting rule', and specifies the ruleRef identifier. It is distinguishable from siblings like 'edit_accounting_rules' and 'preview_accounting_rules', though it could be more explicit about being the opposite of the create/edit paths.

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?

It provides guidance on when to use this tool: when you want to remove a rule from active use. It also advises to preview the impact first when consequences are uncertain, which implies a cautionary note but does not name the preview tool explicitly. Slightly more could be said about when not to use it.

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