trigger-compliance-check

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

Description lacks annotations and does not disclose behavioral traits such as side effects, idempotency, rate limits, or whether the operation is asynchronous. 'Forces' suggests possible blocking or resource-intensive action but no details.

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?

Single sentence with no wasted words. Purpose is front-loaded and immediately clear.

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?

For a zero-parameter, no-output-schema tool, the description adequately states the action. Minor gap: no mention of whether the check runs synchronously or if there is a confirmation/result.

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?

Schema has zero parameters with 100% coverage. Description correctly implies no input needed, adding no confusion.

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?

Specific verb 'run' and resource 'compliance deadline check' clearly define the action. Distinguishes from siblings like 'get-compliance-report' which retrieves data rather than triggering an 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?

Implied usage for manually triggering a periodic check, but no explicit guidance on when to use this vs. alternatives (e.g., checking compliance via 'get-compliance-report' or waiting for scheduled runs).

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