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

Annotations already mark this as read-only and non-destructive; the description adds useful behavioral context: the status is live from the registrar, possible outcomes, and an explicit polling cadence warning. This enriches what the annotations alone convey.

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 tight sentences communicate the core state set, the live nature of the data, and polling etiquette without redundancy. Every phrase earns its place.

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 read-only status tool with an output schema and safety annotations, the description covers the domain (registrar transfer lifecycle) and usage behavior sufficiently. It is slightly incomplete only in parameter semantics, but that is captured separately.

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 only 50%, and the description adds no parameter-level meaning. 'domain' is left to its pattern and 'companyId' is only described as a 'UUID value wrapper,' while the description never clarifies which domain/company context these refer to or whether domain is optional.

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 uses a specific verb ('reports') with a clear resource ('a transfer-in's live progress at the registrar') and lists the relevant states. It is immediately distinguishable from sibling formation domain tools like formation_start_domain_transfer and formation_get_domain_auth_code.

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?

It clearly implies this is the status-checking tool for registrar transfers and gives operational guidance to poll sparingly because transfers take days. It does not explicitly name alternatives or state when not to use it, so it misses the top score.

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