ComplianceCow MCP Server

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

Provides useful behavioral context not in annotations: default value (8000), token approximation (2000), and return structure (Dictionary with content or error), but lacks safety info (read-only, encoding, exceptions).

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 Args/Returns sections; front-loaded purpose statement followed by parameter details; no redundant text though Returns section could be omitted given output schema exists.

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 simple read operation but missing critical operational details like encoding assumptions, handling of missing files (exception vs error dict), and maximum file size limits before truncation.

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?

Effectively compensates for 0% schema description coverage by clarifying uri accepts both file:// and path formats, and explaining max_chars purpose with helpful token context for LLM usage.

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 action ('Read content') and resource ('local file'), with 'local' distinguishing it from siblings like read_resource and fetch_output_file that handle remote/cloud resources.

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?

No guidance on when to use this versus read_resource or fetch_output_file, and no mention of file size limits or binary vs text handling.

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