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

With no annotations, the description carries the full burden; it implies a read but never states read-only or permission requirements. It does earn credit for disclosing a real behavioral trait: `all_pages` reconciles IDs/totals and fails rather than returning partial data. Pagination behavior and failure modes for other parameters remain undisclosed.

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?

Two short sentences with no filler, and the `all_pages` caveat is placed up front rather than buried. The terseness borders on under-specification rather than bloat, but nothing is wasted.

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?

An output schema exists, so return values need not be explained, but a six-parameter listing tool with 0% schema coverage and no annotations needs far more than this. The valid values for `kind`, the shape of `filters`, and pagination semantics are all left for the agent to guess.

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 six parameters, so the description must compensate and largely does not. It hints at `kind` (document vs bank/card) and explains `all_pages`, but `page`, `page_size`, `filters`, and `company_name` are given no meaning, format, or accepted values anywhere.

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 and resource — reading AI booking rules — and narrows scope to document vs bank/card rules, which is what the required `kind` parameter selects. It does not explicitly distinguish itself from near-siblings like list_accounting_booking_rules, list_bank_transaction_booking_rules, or get_ai_booking_rule, so an agent must infer the boundary.

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?

No guidance on when to call this versus the sibling list_/get_ variants, and no prerequisites or context conditions. The only usage-adjacent statement is about `all_pages`, which is a behavior note rather than a when-to-use rule.

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