GitMCP

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Perform health check' reveals nothing about what the tool actually does - whether it's a simple status check, a comprehensive system diagnostic, whether it has side effects, what permissions it requires, or what format the results take. This is completely inadequate for a tool with zero annotation coverage.

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?

While technically concise with just two words, this represents under-specification rather than effective conciseness. The description fails to provide the minimal necessary information about what the tool does. Every word should earn its place, but here the words don't provide enough value - they merely restate the tool name without adding useful context or differentiation.

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 complete lack of annotations and no output schema, the description is woefully incomplete. 'Perform health check' doesn't explain what constitutes a health check in this context, what systems are checked, what the expected output format is, or how to interpret results. For a diagnostic tool that presumably returns status information, this minimal description leaves critical gaps in understanding.

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, so the schema fully documents the parameter situation. The description doesn't need to compensate for any parameter gaps. While the description doesn't add any parameter information beyond what the schema provides, this is acceptable given the zero-parameter baseline. A score of 4 reflects that the description doesn't detract from the complete schema coverage.

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 'Perform health check' is a tautology that restates the tool name without adding meaningful context. It doesn't specify what kind of health check, what system or service is being checked, or what constitutes 'health' in this context. While it uses a verb ('perform'), it lacks the specificity needed to distinguish this from other diagnostic tools like 'ping' or 'env_check' in the sibling list.

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 versus alternatives. It doesn't mention any prerequisites, appropriate contexts, or exclusions. With sibling tools like 'ping', 'env_check', and 'auth_test_connection' that might serve similar diagnostic purposes, the absence of usage guidance leaves the agent guessing about when this specific health check is appropriate.

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