get-domain-purchase-status

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

Annotations already indicate read-only (`readOnlyHint: true`) and open-world (`openWorldHint: true`) behavior. The description adds context about polling and state transitions. No contradictions; it complements annotations well.

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-loading purpose and usage, with no wasted words.

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 tool's simplicity (single param, no output schema), the description is sufficient. It explains the polling behavior and state transitions. Minor gap: no expected response format mentioned, but acceptable for a simple poll tool.

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 100% and the description adds context by explaining the parameter's origin (`purchase_id` from `purchase-domain`) and its role in tracking progress, going beyond the schema.

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 clearly states it polls the progress of a domain purchase initiated by `purchase-domain`, specifying the sequence and resource. It distinguishes itself from sibling tools by focusing on purchase status tracking.

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 description explicitly ties usage to the purchase flow, mentioning the `purchase_id` from `purchase-domain` and expected state transitions, guiding when and how to use it.

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