ComplianceCow MCP Server

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

Discloses client-side pagination behavior and clarifies the API retrieves detailed rather than summary data, adding context beyond the null annotations.

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?

Well-structured with clear sections, but overly verbose in documenting return values (controls list, page, totalPage, etc.) that should be delegated to the existing output schema.

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?

Adequate for simple 2-parameter tool but incomplete due to the parameter name mismatch and redundant return value documentation despite presence of output schema.

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?

Critical mismatch: description references 'review_period' but schema expects 'period'; while semantic descriptions are provided for both parameters, the naming discrepancy could cause invocation failures with 0% 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?

Clearly states it retrieves detailed control-level data (not aggregated) for a specific CCF and review period, though it doesn't explicitly name the sibling aggregation tool (fetch_dashboard_framework_summary).

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?

Explicitly states when to use (for detailed item-level data) and when not to use (does not return aggregated overview), but lacks specific alternative tool recommendations.

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