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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is well covered. The description adds domain scope (provisioning, campaign creation, launch) but does not disclose polling semantics, error behavior, or the exact shape of the returned state.

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?

A single front-loaded sentence with no filler: it states the verb, resource, and parameter in one pass. Every word contributes to understanding the tool's purpose.

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 one-parameter, read-only tool, annotations cover the safety profile and the description gives a clear purpose. However, with no output schema, the description underspecifies what 'current state' actually contains (possible values, structure, or failure semantics), which limits the agent's ability to fully predict 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?

The schema provides only type and format for operation_id, with 0% description coverage. The description adds context that this ID refers to an operation in provisioning, campaign creation, or launch work, but otherwise mostly restates the parameter's obvious role.

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 uses a specific verb ('Returns') and a specific resource ('current state ... by operation_id'), scoping to provisioning, campaign creation, or launch work. It clearly separates get_operation from siblings like get_reply or get_usage in subject matter, though it does not explicitly name alternatives.

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 phrase 'current state' implies a monitoring or polling use case for checking operation progress. It does not explicitly state when to prefer this over sibling tools or when not to use it, leaving some inference to the agent.

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