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

No annotations are provided, so the description carries the full burden. It discloses only that costCenterId assignment is included in the results; it says nothing about pagination behavior, ordering, permissions required, or whether unrelated rule fields are returned. For a tool with zero annotation coverage this is thin.

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 front-loaded sentence with no filler. It is appropriately sized for what it says, though the brevity reflects under-specification rather than tight writing.

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 4-parameter list tool with no annotations and no output schema, the description omits filter semantics, pagination, and the shape of returned rules. The one detail it gives (costCenterId assignment) is useful but far from complete.

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% and there are four parameters (page, page_size, company_name, filter_request). The description mentions none of them and provides no meaning for the opaque filter_request object, so it does not compensate for the schema gap.

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 gives a verb ('Read') and resource ('expense/accounting rules'), and it adds that costCenterId assignment is included, which helps distinguish it from siblings like list_bank_transaction_booking_rules. However, the verb 'read' does not make clear this is a paginated list operation vs. the singular get_accounting_booking_rule, leaving the list-vs-get distinction to the tool name alone.

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 about when to call this tool rather than get_accounting_booking_rule, list_bank_transaction_booking_rules, or list_ai_booking_rules. No prerequisites, no exclusions, no hint that this is the paginated enumeration variant.

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