ComplianceCow MCP Server

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

Documents return values (success boolean, optional error string) but omits critical behavioral details like whether deletion is permanent, idempotent, or has cascading effects on related assessments.

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?

Appropriately concise with structured Args/Returns format; every line conveys essential information without redundancy.

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 single-parameter delete operation but lacks important context regarding the asset/assessment terminology discrepancy and destructive implications of the operation.

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 clearly defining scheduleId as 'ID of the schedule to delete', providing necessary semantic context missing from the raw 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 the delete action clearly but uses 'assessment schedule' terminology that conflicts with tool name 'asset_schedule' and sibling tool 'list_asset_schedules', creating ambiguity about the target resource.

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 versus alternatives like schedule_asset_execution, or conditions under which deletion might fail.

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