ComplianceCow MCP Server

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

Adds critical behavioral detail about 'exact, case-sensitive match' not present in schema, but omits what happens when workflow doesn't 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?

Appropriately brief and front-loaded; Args section is slightly informal but efficient given schema lacks descriptions.

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 a single-parameter tool with output schema, but missing sibling differentiation and error behavior that would make it fully complete.

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 for 0% schema description coverage by defining the 'name' parameter as 'workflow name to search', adding necessary semantic context.

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 retrieves workflow configuration by name with exact matching, but doesn't differentiate from sibling 'fetch_workflow_details' or clarify what 'configuration' includes.

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?

Lacks explicit guidance on when to use this vs 'list_workflows' (when exact name unknown) or error handling if workflow not found.

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