GitMCP

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. 'List backups' implies a read-only operation, but it doesn't specify if it requires authentication, rate limits, pagination, or what the output format looks like (e.g., list of backup names or detailed metadata). This leaves significant gaps for a tool with potential complexity.

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 at two words, with zero wasted language. It's front-loaded and to the point, making it efficient for an agent to parse, though this brevity contributes to gaps in other dimensions.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'backups' entail, how results are returned, or any behavioral traits, making it inadequate for a tool that likely interacts with backup systems and has two parameters.

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 input schema has 100% description coverage, with clear parameter descriptions ('Provider name', 'Repository name'). The description adds no additional meaning beyond the schema, so it meets the baseline of 3 by not contradicting but not enhancing parameter understanding.

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 'List backups' clearly states the verb ('List') and resource ('backups'), providing a basic purpose. However, it doesn't specify what kind of backups (e.g., system, database, file) or differentiate from sibling tools like 'backup_create', making it somewhat vague but still understandable.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing authentication or specific configurations) or compare to related tools like 'backup_create' or 'config_list', leaving the agent with no usage context.

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