ComplianceCow MCP Server

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

Discloses crucial behavioral trait in Returns section: tool returns a 'prompt' string used to generate Cypher rather than actual control data, which is non-obvious from the name.

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?

Structured format (Args/Returns) is good, but opening sentence is wasted space; overall length is appropriate but not optimally front-loaded.

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?

Describes the return value (helpful since output schema exists but isn't shown), but leaves major gaps regarding tool purpose differentiation and control domain context.

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?

Args section compensates for 0% schema description coverage by defining control_name as 'name of the control', adding necessary semantics missing from structured schema.

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?

Opens with tautology 'To fetch controls' that merely restates the tool name, failing to distinguish from siblings like fetch_leaf_controls_of_an_assessment or fetch_dashboard_framework_controls.

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?

Provides no guidance on when to use this generic fetch_controls versus the 10+ specific control-fetching siblings available.

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