blender_ping

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

With no annotations, the description carries the burden and does disclose meaningful behavior beyond the schema: the tool degrades gracefully when Blender is closed, reporting offline status plus locally detected .blend files, and it notes the MCP Add-on requirement for live mode. It does not mention rate limits or side effects, but as a read-only probe the residual risk is low.

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?

Three short sentences, front-loaded with the core purpose before the branching detail. Efficient overall, though the return-value enumeration partially duplicates what an existing output schema already documents.

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 zero-parameter connectivity check with an output schema present, the description supplies the essential context (what is checked, the two operating modes). Nothing an agent needs in order to invoke it correctly is missing; return shape is delegated appropriately to the output schema.

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 per the rubric the baseline is 4. There is nothing for the description to clarify, and it correctly avoids inventing parameter detail.

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 opens with a specific verb+resource — 'Checks the connection status to the Blender Editor' — which is unambiguous. It is clearly distinguishable from all siblings, which read or mutate scene content (get_scene_info, inspect_object, execute_script, etc.); this is the only health/connectivity probe.

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 implies when the tool is relevant by describing the two outcome branches (Blender open vs. closed), but it never explicitly says 'call this first to verify Blender is reachable before invoking other tools' or names any alternative. Usage is inferable rather than stated.

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