operations__get_command_status

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds substantial behavioral context: HTTP 410 handling (outdated ID, stop polling), SDK exception behavior (ApiException with status=410 thrown as is, no separate exception), and throttling of the MCP server (not iikoCloud) with a caching suggestion. This goes well beyond the annotations and fully discloses expected runtime behavior.

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 compact and front-loads the purpose, then adds error handling, ID sourcing, and throttling guidance. Each line adds value with no fluff. It uses line breaks to separate concepts, making it scannable. It is not overly verbose but could be slightly tighter by merging the ID sourcing note, so a 4 is appropriate.

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 status polling tool with no output schema, the description covers the essential aspects: what it does, the possible statuses, the error condition (HTTP 410) and how to handle it, where to get the required ID, and rate-limiting guidance. It does not explain the exact response format (beyond status values) or the polling loop mechanics, but these are not critical for a caller. The presence of a sibling operations__wait_command suggests potential overlap, but the description is self-sufficient.

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 input schema already provides descriptions for both correlationId (operation ID) and organizationId (organization the correlation belongs to), so the schema coverage is high. The tool description adds only one extra hint: where to get organizationId (via organizations__get_organizations). It does not add meaning for correlationId beyond the schema. Given the baseline of 3 for high schema coverage, the marginal addition justifies a 3.

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 the tool returns the status of a command by correlation_id, listing the possible values (Success/InProgress/Error). It clearly identifies the verb ('get status') and resource ('command by correlation_id'), which is specific enough to distinguish it from generic getters. However, it does not explicitly differentiate from the sibling operations__wait_command, which likely waits for a status rather than returns it, so it stops short of a 5.

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 gives clear usage context: it is for polling status, and HTTP 410 signals that the correlationId is outdated and polling should stop. It also instructs where to obtain organizationId (via organizations__get_organizations) and warns about MCP server throttling (60 requests/60s) with a recommendation to cache results. These are explicit usage rules, though it does not mention alternatives like operations__wait_command, so it lacks explicit exclusions.

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