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

Annotations already declare readOnly, idempotent, non-destructive and closed-world. The description adds genuinely new behavior: results come from saved rules and no external service refresh is triggered, which matters for avoiding side effects on provider APIs. It does not describe ordering, pagination, or what an empty result means.

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?

One front-loaded sentence with no filler; the core action ('read saved vendor-to-account rules') comes first and the two qualifiers follow.

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 single-parameter read tool with full annotation coverage and no output schema, the description covers what it reads and what it does not do. Minor gap: no hint at the fields a vendor rule carries (vendor, account, match criteria), which an agent may need before calling.

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 has to compensate. It does clarify that provider filtering is optional even though the 'input' wrapper is required, but it never explains that omitting provider returns rules across all providers, nor enumerates the allowed provider values (only the schema enum does that).

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: reading saved vendor-to-account posting rules, with an optional provider filter. This clearly separates it from save_vendor_rule, delete_vendor_rule and the preview_* siblings, though it never names those siblings explicitly.

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?

Usage is implied rather than stated: 'optional filtered' plus 'without refreshing external services' tells an agent this reads persisted config rather than syncing from QuickBooks/Xero/Zoho. There is no explicit guidance on when to prefer this over a provider-sync path or how it relates to save_vendor_rule.

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