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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the receipt is durable (survives), and calling this never re-triggers/retries the underlying write, so polling is side-effect safe. It says nothing about blocking behavior, possible status values, permissions, or rate limits.

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 core purpose plus the no-retry guarantee are front-loaded. Brevity comes at the cost of clarity in the 'durable exact-company receipt' phrasing.

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 status-lookup tool with a required, undocumented operation_key, the description should at least say where the key comes from and what the call reports. That essential context is absent.

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%, so both parameters are undocumented everywhere. The description does not explain what operation_key is or where to obtain it, nor why the optional company_name exists, which is a significant gap for the only required input.

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 verb 'read' plus 'receipt/status of a rule write' identifies this as a status-polling tool, which does separate it from write siblings like create_ai_booking_rule or update_ai_booking_rule. However, opaque jargon such as 'durable exact-company receipt' obscures what is actually returned, and no sibling (e.g. reconcile_ai_rule_write) is named for differentiation.

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 statement of when to call this, when not to, or what prerequisite produces the operation_key. A related sibling, reconcile_ai_rule_write, exists but is never referenced, leaving the agent to guess which to use.

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