health

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states that the tool checks health, without detailing what that entails (e.g., connectivity, latency, component status), whether it is read-only, or what the response looks like. The description is too sparse to provide meaningful behavioral insight.

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 a single, short sentence that immediately conveys the tool's purpose. There is no fluff or redundant information; every word contributes to clarity and it is front-loaded.

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 low complexity (0 parameters, no output schema), the description might be minimally adequate for a health check, but it lacks any explanation of return values, success/failure semantics, or what 'health' means. For a tool with no annotations or output schema, the description should offer just a bit more context, so a score of 3 reflects a bare-minimum completeness.

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 and the schema is trivially fully covered. Per the rubric, a baseline of 4 is appropriate for 0-parameter tools, and the description adds no unnecessary parameter information.

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 uses a specific verb 'Check' and clearly names the resource 'LiveBrain MCP health', making the tool's purpose unmistakable. It naturally distinguishes itself from the sibling tools (live_set_snapshot and generate_bassline), which are unrelated to health checks.

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 the tool is for verifying system health but does not provide explicit guidance on when to use it versus alternatives, nor does it mention any prerequisites or exclusions. The usage context is apparent from the tool's name and description, but no explicit when/when-not is given.

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