compliance_check

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

No annotations are provided, so the description carries the full burden. It discloses a rate limit (10 checks per day) but does not explicitly state whether the tool is read-only or destructive. It also doesn't describe the output format or side effects, leaving some ambiguity for a compliance check tool.

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?

The description is two sentences long, with no unnecessary words. The first sentence states the purpose, and the second adds constraints and scope. It is front-loaded and efficient.

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?

Given the tool has no output schema and no annotations, the description is fairly complete for a simple check tool. However, it lacks details about the return format (e.g., pass/fail, risk score) and any prerequisites for using the tool. It touches on constraints but not on usage context beyond the free tier.

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?

All three parameters are fully described in the input schema (100% coverage). The description adds no additional meaning beyond what the schema already provides, such as the framework enum and descriptions. Therefore, it meets the baseline for schema coverage.

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?

The description clearly states it performs a 'quick compliance check against common AI governance frameworks', specifying the exact frameworks (EU AI Act, Colorado AI Act, NIST AI RMF, ISO 42001). The verb 'check' distinguishes it from sibling tools (audit_trail, govern_action) which imply deeper audit or action.

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?

The description does not explicitly say when to use this tool versus siblings. It implies a quick preliminary check but provides no guidance on when to prefer it over audit_trail or govern_action. The free tier limit is mentioned, which indirectly suggests usage constraints.

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