asset.operation_result

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the risk level ('read') and maturity level ('L1'), which is useful context beyond the annotations. However, it does not disclose what happens if the taskId is invalid, whether the result is polled or one-shot, or how the result is returned, though the output schema may cover the return shape.

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-loaded with the command name, but it spends its only substantive sentence on generic policy requirements ('Per-request argument checks and session policy still apply') rather than explaining the tool's purpose. It is concise but not optimally structured for an agent deciding whether to call it.

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 tool that retrieves operation results, the description is incomplete. It does not explain what an 'asset operation' is, how to obtain a `taskId`, whether the result is synchronous or asynchronous, or how this differs from `blender_provider_query_result` and `blender_job_status`. The output schema exists but the description still needs to convey the polling/retrieval semantics.

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 50%, with `_requestId`, `_authorization`, and `_transactionId` having descriptions, but the two required parameters `providerId` and `taskId` have no descriptions. The description does not explain what `providerId` and `taskId` refer to or how they relate to the operation result. Since the required parameters are undocumented in both schema and description, the description does not compensate for the gap, but the baseline is 3 because coverage is not extremely low.

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 identifies the tool as a PartMe Blender Harness command named `asset.operation_result`, which implies it retrieves the result of an asset operation, but it never states what the tool actually does in plain terms (e.g., 'fetch the result of a previously submitted asset operation'). The name and title are essentially restated, and the description does not distinguish it from sibling tools like `blender_provider_query_result` or `blender_job_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 provides no guidance on when to use this tool versus alternatives. It mentions that per-request argument checks and session policy apply, but that is a generic requirement, not usage guidance. There is no mention of prerequisites, when to call it after an operation, or how it relates to `blender_provider_query_result` or `blender_job_status`.

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