ComplianceCow MCP Server

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

Discloses that the return value is a Dict with 'complete rule structure and metadata', but provides no information on error conditions, authentication requirements, or rate limits given absence of annotations.

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?

Uses standard docstring format (Args/Returns) with front-loaded purpose statement; appropriately terse though the Returns description is somewhat vague ('complete rule structure').

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?

Sufficient for the low complexity (single string parameter) and given existence of output schema, but incomplete due to missing sibling differentiation and lack of parameter constraints.

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?

Adds minimal semantic meaning ('Rule name of the rule to retrieve') beyond the 0% schema coverage, though it fails to specify format constraints, case sensitivity, or examples for the rule_name parameter.

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 fetches rule details by name from ComplianceCow, distinguishing from fetch_cc_rule_by_id via the 'by rule name' specification, though it doesn't clarify relationship to the generic fetch_rule sibling.

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 tool versus alternatives like fetch_cc_rule_by_id or fetch_cc_rules_list, leaving selection to inference from the tool name alone.

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