get_bundle_operation

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

Given no annotations, the description covers key behaviors: it's a polling operation, lists possible statuses, and implies non-destructive behavior. Does not mention rate limits or error handling, but for a simple poll this is adequate.

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?

Extremely concise: three sentences, each with clear purpose. Front-loaded with action and resource, no redundant information. Every sentence 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 simple polling tool with one parameter and no output schema, the description is almost complete. It explains purpose, statuses, when to call, and prerequisites. Could optionally mention timeout or error conditions, but not essential.

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% (operation_id described in schema). The description adds value by explaining that the ID comes from create_bundle or update_bundle results, providing context beyond the schema's generic 'GID' description.

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 status of an asynchronous bundle operation, using specific verb ('poll') and resource ('bundle create or update operation'). It distinguishes from siblings like get_bundle (which likely retrieves bundle details) by focusing on status polling.

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 this after create_bundle or update_bundle until status is COMPLETE.' Also states required scope ('Requires read_products scope'). Provides clear context without mentioning alternatives, which is sufficient.

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