ComplianceCow MCP Server

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

With no annotations provided, description carries full burden but only discloses return type; misses idempotency, side effects, or failure modes beyond basic purpose.

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?

Docstring format (Args/Returns) is well-structured and front-loaded; every line conveys necessary information without redundancy, though Returns section partially duplicates existing output schema.

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?

Incomplete regarding complex app_info parameter structure (accepts arbitrary additionalProperties); fails to specify required fields or format for application objects, leaving critical usage information undefined.

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 coverage by defining rule_name clearly, but app_info description ('List of application objects') is tautological and lacks crucial details about required object properties despite additionalProperties: true in 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?

States specific action (publish) and outcome (make available for rule execution) but fails to distinguish from siblings like prepare_applications_for_execution or publish_rule.

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 (prepare_applications_for_execution, publish_rule) or prerequisites for publishing.

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