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

With no annotations, the description carries the full burden; 'Read' implies read-only but nothing confirms safety or side effects. It omits pagination behavior (page/page_size defaults), what filter_request accepts, and how company_name scoping affects results.

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?

A single compact sentence with the resource front-loaded and no filler. It is efficient, though the brevity is partly the cause of the missing guidance rather than a virtue in itself.

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?

No output schema, no annotations, and four undocumented parameters including an opaque filter object. For a paginated list tool whose filtering contract is unspecified, the description leaves the agent without enough to call it correctly beyond bare defaults.

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% across all four parameters, and the description does not compensate: page, page_size, company_name, and especially the free-form filter_request object are never explained. Mentioning costCenterId refers to a returned field, not an input, so it adds no parameter guidance.

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?

States a specific verb ('Read') and resource ('bank transaction rules') and names two returned fields, so the agent knows what it gets back. It does not distinguish itself from the sibling get_bank_transaction_booking_rule or clarify whether this returns all rules versus a filtered set.

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?

There is no guidance on when to use this versus get_bank_transaction_booking_rule, list_accounting_booking_rules, or list_ai_booking_rules, nor any stated precondition such as needing a company_name. The agent must infer the choice entirely from the name.

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