ComplianceCow MCP Server

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

Without annotations, the description only provides one behavioral hint: that the ID must be sourced from 'get_workflows' output path /status/id; misses side effects, validation rules, or idempotency.

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?

Concise but poorly structured: lacks front-loaded purpose statement, diving immediately into 'Args:' without context.

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?

Incomplete for the workflow tool ecosystem; fails to clarify relationship to 'create_workflow' or 'modify_workflow', and omits expected Mermaid syntax/format constraints despite having output schema available.

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 by explaining where to fetch the 'id' parameter, though 'mermaidDiagram' receives only tautological elaboration.

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; it only lists argument definitions without stating that the tool updates or sets the workflow's Mermaid diagram.

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 no guidance on when to use this versus siblings like 'modify_workflow' or 'update_workflow_summary', or prerequisites for the diagram format.

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