Promotion: order status

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

Annotations already indicate readOnlyHint and destructiveHint false. Description reinforces with 'READ-ONLY: spends NO money.' Adds value beyond annotations by explicitly stating financial impact (spends no money) and specifying return fields.

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 concise sentences: first states purpose and return fields, second declares read-only nature, third gives usage guidance. No filler, front-loaded with essential info.

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 single-parameter read-only tool, description fully covers what it does, what it returns, and when to use it. No gaps given lack of output schema.

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% with orderId described as 'Promotion order identifier in UUID format...'. Description adds context by explaining the return value relationships, but parameters are well-covered in 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?

Description clearly states 'Returns the status of a BBIP order by its orderId' and lists return fields (overall status, totalPrice, per-item status). Specifies exact verb+resource and distinguishes from sibling promotion_create_bbip_order_for_items_v1 by indicating this is for tracking after 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 tells when to use: 'Call it AFTER promotion_create_bbip_order_for_items_v1 to track the order's execution.' Clearly communicates the sequential usage pattern without ambiguity.

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