ping_blender

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

With no annotations, the description carries the full burden. It transparently states this is a read-only check that reports current state (open file, version, scene). It doesn't explicitly mention side effects (none implied) or error behavior, but for a simple ping-style tool, this is adequate. The description provides more behavioral context than a bare 'ping' would.

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, front-loaded sentence with no wasted words. The purpose is stated first, followed immediately by the expected output. Every word earns its place.

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?

The tool is simple, has no parameters, and the output schema already documents the return values, so the description only needs to convey the intent and scope. It does so clearly enough for an agent to know what to expect. It falls short only because it doesn't mention when to use it (e.g., as a health check), but given the simplicity, this is a minor gap.

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?

There are zero parameters and schema coverage is 100%, so the schema fully describes the input surface. The description doesn't need to add parameter details, and it doesn't mislead. The baseline for zero params is 4, and the description appropriately focuses on behavior rather than parameters.

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 clearly states the verb 'check' and the resource 'Blender bridge', and specifies exactly what it reports: open file, Blender version, and scene. It distinguishes itself from the sibling inspection tools (e.g., inspect_scene, inspect_object_animation) by focusing on connectivity/status rather than detailed scene analysis.

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 the many alternative inspection tools. It doesn't mention that it's a lightweight health check or that inspect_scene might be more appropriate for deeper scene queries. An agent would need to infer usage context from the name and description.

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