ComplianceCow MCP Server

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

Discloses timeout risks, large payload handling, and pagination requirements compensating for missing annotations; no contradictions.

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?

Verbose with mixed formatting (narrative, numbered list, pseudo-docstring Args/Returns); the 4-step workflow is helpful but overly prescriptive for agent 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?

Adequately covers the tool's complexity including pagination workflow and dependency on sibling tool; output schema exists so detailed Returns section is redundant but not harmful.

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 explicitly defining 'id' as Asset run id and explaining pagination parameters in context of timeout handling.

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?

States specific action (Get resource types) and target resource, and explicitly references sibling tool 'fetch_assets_summary' to distinguish prerequisite workflow.

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?

Excellent explicit guidance: mandates using 'fetch_assets_summary' first, describes when to use pagination (large responses/timeouts), and provides specific retry strategy (50→100 pageSize).

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