ComplianceCow MCP Server

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

With no annotations provided, description fails to explain critical behavioral logic: what criteria determines 'top' overdue controls (days overdue, priority, count?) and omits sorting/ranking behavior.

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?

Uses structured Args/Returns format but contains unnecessary repetition, typo ('donates' for 'denotes'), and redundant parenthetical '(over-due)' that adds no value.

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?

Includes detailed return schema which satisfies output documentation, but lacks explanation of the ranking logic essential for a 'top N' query tool with simple 2-parameter input.

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?

Compensates partially for 0% schema coverage: 'period' explanation adds value (quarter format, dashboard context), but 'count' description is tautological ('accepts count as count').

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?

States it fetches overdue controls but has redundant phrasing 'over due (over-due)' and fails to distinguish from sibling 'get_top_non_compliant_controls_detail' or explain what 'top' means.

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 on when to use this vs alternatives like fetch_controls or get_top_non_compliant_controls_detail; only lists parameter inputs.

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