ComplianceCow MCP Server

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

No behavioral traits disclosed (e.g., what details are returned, caching, or side effects) beyond the implicit parameter requirement.

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?

Structurally flawed: formatted as an 'Args:' section without a main description body; though brief, the missing purpose statement makes it incomplete.

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 only one parameter and an existing output schema, the description is incomplete because it omits the core function, leaving the agent to infer purpose solely from the tool name.

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 well for 0% schema coverage by clearly defining 'id' as 'workflow id' and specifying the exact JSONPath '/status/id' in 'get_workflows' output to source it.

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?

Description lacks a purpose statement entirely, only documenting the 'id' parameter without stating what 'fetching workflow details' entails or returns.

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 minimal guidance on sourcing the ID from 'get_workflows', but fails to differentiate from siblings like 'get_workflow_by_name' or indicate when to use this tool.

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