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

With no annotations, the description carries the full behavioral burden. It usefully discloses that this is a read operation returning a revision for drift checking, but it omits permission requirements, error behavior, and any detail about how the revision should be used during edits.

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?

The description is a single front-loaded sentence with no wasted words. It puts the verb and core resource first and adds the drift-check context compactly.

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 in detail. However, for a getter with 0% schema description coverage and no annotations, the one-sentence description is too thin on parameter meaning and operational context.

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 the description does not explain any of the three parameters. It gives no meaning for kind, rule_id, or the optional company_name, leaving the agent with undocumented required inputs.

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 read operation and adds that it returns a mutable-field revision. However, it calls the resource only 'a rule' and does not distinguish this from sibling getters such as get_accounting_booking_rule or get_bank_transaction_booking_rule.

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 phrase 'for a drift-checked edit' implies the intended workflow context, but it does not explicitly say when to use this tool versus list_ai_booking_rules, describe_ai_booking_rules, audit_ai_booking_rules, or the other rule getters.

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