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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-obvious context: it does NOT auto-start Desktop and does NOT execute a Blender command — an important boundary for an agent that might otherwise assume reading state triggers a process. It stops short of describing failure/error behavior when Desktop is not running, which keeps it at 4.

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 the action and target, followed by the field list, the negative boundaries, the use case, and sibling routing — in that priority order. Every sentence carries a distinct, load-bearing job.

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?

No output schema exists, and the description compensates by listing what state is returned. It also covers the two behavioral risks an agent would face (no auto-start, no command execution) and resolves all four sibling overlaps. Nothing needed to call it correctly is missing.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The enumeration of returnable fields (version, account access, Bridge, workspace, extension, chats, language, updates) is the only parameter-adjacent value and it is already covered by the no-param structure.

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 ('the receiving Blender Bridge Desktop application's configuration and status'), then enumerates the exact fields returned. An agent can distinguish it from metadata tools like get_connection or get_setup_status without opening any schema.

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?

Explicitly scopes usage to 'Desktop settings and process diagnostics' and names three alternatives with the condition that selects each: get_connection for chat account computers/collaboration, get_setup_status for full connection diagnosis, get_scene_state for scene content. 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.