ComplianceCow MCP Server

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

Discloses critical behavioral trait that only active functions are returned, and details return structure comprehensively since no annotations exist

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 but verbose due to extensive Returns documentation that may duplicate 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?

Comprehensive coverage of purpose, filtering behavior, and return values despite existing 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?

No parameters exist, meeting baseline requirement

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?

Clear specific purpose with verb 'Retrieve' and resource 'workflow functions', distinguishes from siblings like list_workflows by defining functions as core actions for nodes

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 implied usage context by explaining functions are for workflow nodes, but lacks explicit when/when-not guidance versus similar tools like list_workflow_activity_types

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