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. 'Test connectivity' implies a read-only diagnostic operation, but it doesn't specify what happens during the test (e.g., whether it pings a network, checks API endpoints, or validates configurations), what the expected output looks like, or any side effects. This leaves significant gaps in understanding the tool's 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 extremely concise with just two words, 'Test connectivity', which is front-loaded and wastes no space. For a simple diagnostic tool with no parameters, this brevity is appropriate and efficient.

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 tool's simplicity (no parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what 'connectivity' means in this context, what the test entails, or what result to expect. For a diagnostic tool, more context on behavior and output would be helpful, even without structured fields to compensate.

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 description coverage is 100% (though trivial since there are no parameters). The description doesn't need to explain parameters, and it appropriately doesn't mention any. This meets the baseline expectation for a parameterless tool.

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 'Test connectivity' states what the tool does at a basic level, but it's vague about what exactly is being tested. It doesn't specify what resource or service connectivity is being tested, nor does it differentiate from sibling tools like 'health_check' or 'auth_test_connection' which might serve similar diagnostic purposes.

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. There's no mention of prerequisites, appropriate contexts, or comparisons to sibling tools like 'health_check' or 'env_check' that might also test system status. The agent must infer usage from the name alone.

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