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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond annotations: MCP clients cannot approve operations, the target API is SmartShifts organization workforce API, and provider record text is untrusted data. It does not contradict the annotations.

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 short and front-loads the core action, then adds operational and security context. The documentation and untrusted-data sentences are useful but slightly boilerplate, keeping it from a 5.

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-check tool with rich annotations and an output schema, the description is largely complete. It covers the action, ownership scope, approval restriction, target API, and untrusted-data warning, though it omits polling behavior and sibling-tool differentiation.

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?

There is one required parameter, operationId, and schema description coverage is 0%, so the schema provides no meaning for it. The description only implies that operationId refers to an operation owned by this connection; it does not explain format, provenance, or how to obtain the ID.

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 specific verb and resource: 'Check an operation owned by this connection.' It is clearly about operation status, reinforced by the title 'Check organization change status,' but it does not explicitly distinguish itself from the sibling tool system_workflow_status.

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 no guidance on when to use this tool versus alternatives such as system_workflow_status, nor does it state when not to use it. The statement 'MCP clients cannot approve operations' is a behavioral constraint, not usage guidance.

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