Bernstein - Multi-agent orchestration

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

With no annotations provided, the description carries full burden and does well: it discloses the tool always succeeds if server is running (key behavioral trait), specifies it returns JSON with status 'ok', and implies it's a read-only diagnostic operation. It doesn't mention rate limits or authentication needs, but for a simple health check, this is reasonably complete.

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?

Perfectly structured and concise: purpose statement first, usage guidance second, return value third. Every sentence earns its place with zero waste. The description is appropriately sized for a simple health check tool.

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 with output schema, the description is complete: it explains purpose, when to use, behavioral characteristics (always succeeds if running), and return format. No additional context is needed given the tool's simplicity and the presence of 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 has 0 parameters with 100% schema coverage, so baseline would be 3. However, the description explicitly states 'always succeeds if the MCP server is running' which adds meaningful context about the tool's behavior that goes beyond the empty parameter schema, justifying a higher score.

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 tool's purpose with specific verbs ('Liveness check', 'verify connection') and resource ('Bernstein MCP connection'), distinguishing it from siblings like cost or task management tools. It explains exactly what the tool does: verify server connectivity and always succeed if running.

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?

Explicit guidance is provided: 'Use this to verify the Bernstein MCP connection is still alive.' This clearly indicates when to use this tool versus alternatives - specifically for connectivity verification rather than operational tasks like running, stopping, or checking status of Bernstein operations.

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