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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds real context beyond that with the prerequisite of a production-ready receiving Bridge and Blender, and the shape of what comes back. The closing 'does not modify the scene' largely restates destructiveHint=false, and it omits failure behavior (e.g., what happens if the Bridge isn't ready).

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?

Front-loaded with purpose and return payloads, followed by prerequisites, then usage alternatives. Roughly four sentences, all earning their place except the final 'does not modify the scene' clause, which duplicates the annotations.

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?

There is no output schema, so the description correctly enumerates the returned fields; with annotations covering the safety profile and zero parameters, what remains — prerequisites, use case, alternatives, side-effect status — is all present.

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 no parameter semantics to explain; the baseline for a 0-param tool applies. The description wastes no effort inventing parameter detail and instead spends its words on returns and routing.

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?

States a specific verb (read) and resource (version/protocol diagnostics plus scene summary from a ready Blender runtime), and names the concrete return payloads (server_info, Bridge/add-on contracts, scene_summary). Siblings like get_scene_state, check_connection and take_screenshot are explicitly differentiated.

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?

Explicit when-to-use ('diagnose runtime or version compatibility') plus three named alternatives with the condition that selects each: get_scene_state for detailed inspection, check_connection for readiness only, take_screenshot for visuals. Nothing is left to inference.

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