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

With no annotations, the description carries the full burden for a mutation tool, and it omits the most important behavior: the schema defaults dry_run=true and explicit_enable=false, so a naive call likely changes nothing. Whether the operation is reversible, what permissions it needs, and what constitutes success are all 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?

One short sentence with the key differentiator front-loaded and no filler. It is arguably too terse rather than too long, but structurally it is clean.

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 for a four-parameter mutation with zero annotation coverage and 0% schema description coverage the description leaves an agent unable to call it correctly on the first try. The dual dry_run/explicit_enable safety mechanism must be documented somewhere and is currently absent from every field.

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 four parameters, so the description must compensate entirely and it explains none of them. In particular the double gate of dry_run (default true) and explicit_enable (default false) is non-obvious and would be the single most valuable sentence to include, along with what rule_ids refer to.

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 (enable automatic booking) and explicitly severs the operation from rule CRUD, which helps an agent avoid the update_* siblings. It does not, however, distinguish itself from close siblings like set_bank_transaction_booking_rule_activation or set_ai_booking_rule_auto_booking, so an agent still has to guess which activation path applies.

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 clause 'deliberately separate from rule CRUD' implies this is the correct entry point for enabling autobooking rather than mutating the rule, but no alternative tool is named and no when-not condition or prerequisite (e.g. rule must exist, must be inactive) is given.

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