ComplianceCow MCP Server

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

Discloses error handling behavior ('Error message if retrieval fails or README not available') but omits other traits like caching, rate limits, or auth requirements since no annotations are provided.

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 front-loaded purpose statement and clear Args/Returns sections; slightly verbose but every sentence adds value beyond the structured fields.

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?

Adequately complete for a simple retrieval tool with one parameter; the Returns section documents output despite the presence of an output schema, ensuring clarity without redundancy.

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 specifying the 'name' parameter requires the 'exact name' of the rule, adding crucial semantic constraints not present in the bare schema.

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 README documentation for a rule by name, distinguishing it from siblings like `fetch_rule` (which gets the rule itself) and `fetch_task_readme` (which targets tasks).

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 context ('useful for understanding how to properly use a rule') but lacks explicit guidance on when to use this vs. siblings like `create_rule_readme`, `update_rule_readme`, or `generate_rule_readme_preview`.

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