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. 'Check environment variables' implies a read-only operation, but it does not specify what the tool returns (e.g., a list, a status report), whether it has side effects, or any constraints like permission requirements or rate limits. This leaves significant gaps in understanding the tool's behavior beyond the basic action.

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 'Check environment variables' is a single, efficient phrase that directly states the tool's purpose without unnecessary words. It is appropriately sized for a simple tool, though it could be slightly more informative without losing conciseness. There is no structural waste, but it lacks depth that might be beneficial for clarity.

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 (0 parameters, no output schema, no annotations), the description is incomplete. It does not explain what 'checking' entails or what the output might be, leaving the agent unsure of the tool's full functionality. For a tool with no structured data to rely on, the description should provide more context to be fully helpful.

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, meaning the schema fully documents the absence of inputs. The description does not add any parameter information, which is appropriate since there are no parameters to explain. This meets the baseline for tools with no parameters, as there is no need to compensate for schema 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 'Check environment variables' clearly states the verb ('Check') and resource ('environment variables'), providing a basic understanding of the tool's function. However, it lacks specificity about what 'checking' entails (e.g., listing all variables, verifying specific ones, validating values) and does not distinguish it from potential sibling tools like 'config_get' or 'config_list', which might overlap in functionality. This makes it vague but not misleading.

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 does not mention any context, prerequisites, or exclusions, such as whether it's for debugging, configuration validation, or system health checks. With sibling tools like 'config_get' and 'health_check' that might serve similar purposes, the lack of differentiation leaves the agent without clear usage instructions.

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