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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuine context beyond that: it does not execute Blender or block waiting on it. It stops short of saying what state is actually returned or how stale it might be.

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 sentence with no waste, front-loading the panel scope and the key behavioral guarantee (no execution, no waiting). Nothing to trim.

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?

With zero params and rich annotations, most of the burden is already handled by structured fields. The one residual gap is that no output schema exists, so the description could say what 'operation state' actually contains, but for a simple panel read this is close to complete.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Schema coverage is 100% and the empty properties object matches the no-argument nature of the call.

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 names a specific verb ('read') and resource ('long-operation state') and scopes it to the Blender panel, so the agent knows it retrieves in-progress operation info without side effects. It doesn't, however, distinguish itself from the similarly named sibling get_blender_operation_status, leaving some ambiguity about which to pick.

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?

It conveys implied usage – check progress without triggering or waiting on Blender – which is a useful non-blocking hint. But it never explicitly says when to use this versus get_blender_operation_status or get_scene_state, nor does it state any prerequisites, so routing depends on inference.

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