mcp-adr-analysis-server

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. It mentions security features and test requirements but lacks details on critical behaviors like authentication needs, rate limits, error handling, or what happens during pushes (e.g., whether it modifies history). The description is insufficient for a mutation tool with complex parameters.

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 two sentences but includes some redundancy (e.g., 'AI-driven' and 'calling AI') and could be more front-loaded. The second sentence about tests feels tacked on rather than integrated, reducing overall efficiency.

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 complexity (7 parameters, nested objects, no output schema, and no annotations), the description is inadequate. It doesn't explain return values, error conditions, or the full scope of 'security-focused' features, leaving significant gaps for an AI agent to understand tool behavior.

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?

Schema description coverage is 100%, so the schema already documents all 7 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema, such as explaining interactions between parameters or providing examples. This meets the baseline for high 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 clearly states the tool performs an 'AI-driven security-focused git push' with specific features like credential detection, file filtering, and deployment metrics tracking. It distinguishes itself from generic git push operations by emphasizing AI-driven security features, though it doesn't explicitly differentiate from sibling tools since none appear to be git-related.

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 'Tests should be run by calling AI and results provided,' suggesting this tool should be used when AI-executed test results are available. However, it doesn't provide explicit guidance on when to use this tool versus alternatives or when not to use it, leaving some ambiguity about prerequisites.

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