roamzy_order_status

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

No annotations provided, but description explains status progression, response includes msisdn, and user-facing naming guidelines. Does not cover potential side effects or rate limits, but sufficient for a polling tool.

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?

Three sentences, all essential. Front-loaded with purpose, then status flow, then action step. 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?

Covers status progression, next steps, and naming guidance. Lacks full response details but sufficient for a simple polling tool with no output schema. Good for the given 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?

Schema coverage is 100% with description for order_id. Description adds context that it is an internal intent_id from create_order and should not be shown to user, which goes beyond 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?

Clearly states the tool polls status of a pending order and lists status progression. Distinguishes from siblings like roamzy_get_esim (for activation link) and roamzy_create_order (for creation).

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?

Explicitly instructs to call get_esim when status is finished, providing a clear alternative. Also indicates this tool is for pending orders, guiding when to use.

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