system-health

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

The description lists data points (Blender version, open .blend, queue depth, last-error ring buffer) but does not describe the output format, whether the tool modifies any state, or if it has side effects. Its behavior remains unclear.

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?

The description is very brief, consisting of a single sentence with a colon and a list. It is concise and to the point, though the structure is minimal and does not aid comprehension.

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?

Given the lack of annotations and output schema, the description is severely incomplete. It does not explain the tool's purpose, when to use it, what it returns, or any behavioral details, leaving the agent with insufficient information.

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 no parameters, so the description does not need to explain them. However, it also does not add clarity about the tool's output, which is not directly parameter-related. This is a neutral score since parameters are absent.

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 lists 'Bridge health: Blender version, open .blend, queue depth, last-error ring buffer' but does not explicitly state that the tool reports system health status or what action it performs. The tool name suggests a health report, but the description is ambiguous and lacks a clear verb or purpose.

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, under what conditions, or how it differs from other tools. No alternatives or usage scenarios are mentioned, leaving the agent without direction.

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