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

Annotations already indicate readOnlyHint=false (mutation), destructiveHint=false (no deletion), and idempotentHint=false. The description adds value by clarifying that changes are not applied to existing transactions, which is a key behavioral trait. However, it doesn't elaborate on side effects (openWorldHint=true) or any other execution details, so it provides limited additional transparency beyond annotations.

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 efficiently conveys the main actions and scope. It front-loads the purpose and immediately clarifies exclusions, making it easy to scan without unnecessary detail.

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 the complexity (4 operations, nested condition/action schemas, no output schema, no parameter descriptions), the description is grossly incomplete. It doesn't explain the operation parameter, how to structure rules, or what the response will be. The advisory to preview changes is helpful but insufficient for an agent to correctly construct a call without further documentation.

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 description coverage is 0%, so the description must compensate by explaining parameters. It fails to mention workspaceRef, portfolioRef, operation, ruleRef, conditions, action, or orderedRuleRefs. The operation enum values are critical but entirely undocumented in the description. This is a significant gap for a tool with 9 parameters and nested objects.

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 a specific verb (create, update, enable/disable, reorder) and resource (saved accounting rules). It also distinguishes from siblings by explicitly noting what it does NOT do (delete rules, apply to existing transactions), which helps an agent differentiate it from delete_accounting_rule and apply_accounting_rules.

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 explicitly says when not to use this tool: 'without deleting rules or applying them to existing transactions,' which points to using delete_accounting_rule and apply_accounting_rules for those cases. It also advises to 'preview uncertain changes first,' suggesting a workflow step with preview_accounting_rules. This provides clear when and when-not guidance.

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