ComplianceCow MCP Server

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

Since no annotations exist, the description carries the burden well by explaining the interactive workflow requiring user confirmation before execution, though it omits explicit read-only or idempotency statements.

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 with purpose first, then workflow, but includes a verbose Returns section that likely duplicates the output schema; front-loaded value is decent but could trim the returns documentation.

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?

Given the input complexity (4 flat string parameters) and existence of output schema, the description adequately covers the workflow context and relationship to execute_action, though it could clarify what distinguishes evidence-level from control-level actions.

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?

Despite 0% schema description coverage, the Args section provides only tautological descriptions (e.g., 'assessment_name: assessment name') without explaining relationships between parameters or how to obtain valid values.

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?

Clearly states it retrieves actions available for specific evidence, distinguishing from sibling tools like fetch_assessment_available_actions by specifying the evidence resource type.

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?

Explicitly describes the multi-step workflow (fetch → user confirmation → use execute_action) and references the sibling execute_action tool as the alternative for execution.

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