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

No annotations are provided, so the description carries the full behavioral burden. "Get" implies a read, but it does not disclose whether the operation must be in a specific state, what happens if the operation_id is invalid, or any return characteristics.

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?

The description is a single short sentence with no wasted words, and the core action is front-loaded. It is appropriately concise for a simple getter, though the brevity contributes to the definitional gaps noted elsewhere.

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?

There is no output schema and no annotations, and the description does not explain what an operation is, how to obtain its ID, or what the return value contains. For a tool whose parameter is undocumented and whose context is only inferable from siblings, this is inadequate.

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 for the single parameter operation_id is 0%, and the description only implies that it identifies an "existing operation." It does not explain the expected format, origin, or any constraints for the operation_id, leaving the agent to guess.

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 states a clear verb ("get") and resource ("an existing operation"), so the basic purpose is discernible. However, it does not differentiate this tool from its siblings (once_create, once_reconcile, once_retry) or clarify what kind of "operation" is meant, so an agent still has to infer the context.

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 offers no guidance on when to use this tool versus alternatives. It does not mention once_create, once_reconcile, or once_retry, nor does it state any prerequisites for retrieving an operation.

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