ping_blender

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

No annotations are provided, so the description carries the burden of behavioral disclosure. 'Check' implies non-mutating behavior and 'Call this first' implies it is safe, but it doesn't describe what a successful or failed ping returns or explicitly confirm there are no side effects.

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?

Two sentences with no filler. The core check is front-loaded and the second sentence adds practical usage context that 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?

For a zero-parameter health-check tool, the description covers what it does and when to call it. It is slightly incomplete on return/failure semantics and does not distinguish itself from get_bridge_status, but these are minor gaps for a ping tool.

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 has zero parameters, so the schema is trivially complete and the baseline is 4. The description adds no parameter detail, but none is needed for a parameterless ping tool.

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 clear verb ('Check') and resource ('Blender running with AI Bridge started'), and the diagnostic intent is obvious. It doesn't explicitly differentiate from sibling tools like 'ping' or 'get_bridge_status', so it stops short of a 5.

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 says to call this first if any other Blender tool fails to connect, giving a concrete trigger for use. It doesn't mention when not to use it or name alternatives like get_bridge_status, so it lacks full exclusion guidance.

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