Get domain transfer status

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

The description adds context beyond the readOnlyHint annotation by explaining that it maps numeric StatusID to a plain-English meaning and a coarse phase, and it explicitly says 'Read-only.' This provides useful behavioral information about the output transformation without contradicting annotations.

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 concise sentences, front-loaded with the action and key resource, no redundant information.

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?

Given the simple one-parameter tool and the presence of an output schema, the description adequately covers usage. It doesn't need to detail return values or error handling, and it's complete for its complexity.

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?

The input schema already fully describes transferId as 'The TransferID from transfer_domain,' and the description repeats this context without adding new details. With 100% schema coverage, baseline 3 is appropriate.

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 the specific verb 'look up,' names the resource ('status of an in-progress or completed inbound transfer'), and specifies the input (TransferID). It clearly distinguishes itself from sibling tools like transfer_domain and get_domain_info by focusing solely on transfer status.

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 states the TransferID is returned from transfer_domain, implying the tool is used after initiating a transfer. It doesn't explicitly list alternatives, but the context makes the use case clear. This merits a 4 rather than a 5 because no when-not-to-use or alternative is stated.

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