health_check

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the action ('perform a local system health check') and return value ('returns system information and configuration status'), but doesn't specify potential side effects, error conditions, performance characteristics, or authentication requirements. The description provides basic behavioral context but lacks depth for a diagnostic tool.

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 perfectly concise with two sentences that each earn their place. The first sentence states the action and purpose, while the second explains the return value. There's zero wasted language, and the information is front-loaded with the most important details first.

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 no annotations and no output schema, the description provides basic context about what the tool does and what it returns. However, for a health check tool that presumably returns structured diagnostic information, the description could be more complete by specifying what 'system information and configuration status' includes or providing examples of typical output.

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 schema has 100% description coverage for its single optional parameter, so the baseline is 3. The description doesn't add parameter-specific information beyond what's in the schema, but since there's only one optional parameter and the tool's primary function doesn't depend on it, this represents minimal parameter burden. The description focuses appropriately on the core functionality.

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 ('perform', 'verify') and resources ('local system health check', 'Playwright MCP server configuration and connectivity'). It distinguishes itself from sibling tools by focusing on system diagnostics rather than browser interactions like clicking, navigating, or taking screenshots.

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 usage context ('to verify Playwright MCP server configuration and connectivity') but doesn't explicitly state when to use this tool versus alternatives. No guidance is provided on prerequisites, timing, or exclusions, leaving the agent to infer appropriate usage scenarios.

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