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. It discloses that this is a diagnostic operation that returns system information and configuration status, which helps the agent understand it's a read-only check. However, it doesn't mention potential side effects (though likely none), authentication requirements, rate limits, or error behavior.

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 states the action and purpose, the second specifies the return value. It's front-loaded with the core functionality and wastes no words.

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 this is a simple diagnostic tool with no parameters, no annotations, and no output schema, the description provides adequate context about what it does and what it returns. However, without an output schema, more detail about the structure of the returned system information would be helpful for 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 0 parameters with 100% schema description coverage. The description appropriately doesn't discuss parameters since none exist. It adds value by explaining what the tool does without needing to compensate for parameter documentation gaps.

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 specific action ('Perform a local system health check') and the resource ('Postman MCP server configuration and connectivity'), distinguishing it from sibling tools that focus on API/collection/environment management rather than system diagnostics. It explicitly mentions what it verifies and what it returns.

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 by stating it's for verifying server configuration and connectivity, suggesting it should be used for diagnostic purposes. However, it doesn't explicitly state when not to use it or name specific alternatives among the many sibling tools, which are all data operations rather than system checks.

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