get_operation_status

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

With no annotations, the description carries the full behavioral burden and delivers almost nothing. It does not say whether the call blocks while an operation is pending, what happens for unknown or expired operation_ids, whether it requires authentication, or how errors are surfaced; only 'durable' gestures vaguely at persistence.

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?

It is a single front-loaded sentence with no filler, but the brevity comes at the cost of substance rather than being earned. There is nothing to structure because almost nothing is said.

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, so the description should explain what the returned 'result' looks like, including pending/failed states. It only alludes to a result existing, leaving the agent unable to interpret the response.

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 0% and the description mentions neither request_id nor operation_id. The agent gets no explanation of what a 32-character request_id is, where it comes from, or how operation_id relates to it, so the description fails to compensate for the schema gap.

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 verb 'get' and resource 'operation result' are stated, and 'durable' hints at persisted async operations. But it is too terse to distinguish it from siblings like list_operations or get_connection_status, and 'durable' is left undefined.

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?

No guidance on when to call this versus list_operations or get_connection_status, and no mention of prerequisites such as having obtained an operation_id from execute_operation. The agent must infer the workflow entirely.

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