ComplianceCow MCP Server

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

No annotations are provided, so the description carries full behavioral disclosure burden. It misleadingly suggests the tool performs interactive user prompting ('prompt the user: yes/no'), which is atypical for stateless MCP tools and likely describes desired AI orchestration rather than actual tool behavior. It mentions returning a Dict but omits side effects, idempotency, or error conditions.

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 bloated with workflow orchestration details (four bullet points of conditional user interaction) that likely describe how the AI should use the tool rather than what the tool does. These should be removed or moved to system prompts, as they clutter the actual tool specification.

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?

Despite having an output schema, the description focuses excessively on workflow UI logic instead of explaining the return value structure or mutation semantics. For a tool that appears to perform writes (publishing), the lack of safety warnings or state change descriptions is a significant gap.

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?

With 0% schema description coverage, the description compensates by providing 'rule_name: Name of the rule to check' which adequately documents the single required parameter. No additional semantic context (e.g., format constraints, case sensitivity) is provided, but baseline coverage is met.

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 states it checks publication status, but conflates this with complex workflow orchestration (prompting users, conditional publishing). It distinguishes from 'publish_rule' by implying a check-then-publish pattern, but the mixing of tool function with UI workflow steps obscures the actual atomic operation.

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?

Implies a specific workflow context (preparing for control attachment) but fails to explicitly contrast with sibling tools like 'publish_rule' or 'check_rule_status'. The conditional logic described doesn't clarify when to prefer this over direct publishing.

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