arai_check_action

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

With no annotations, the description discloses no execution, no audit log write, and return shape (same as arai_recent_decisions). Sufficient for a query tool but could mention error behavior.

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?

Two focused sentences, no redundancy. First sentence defines purpose and key behavior; second sentence adds usage and returns.

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 purpose, behavior, usage, and relationship to sibling tool. Lacks details on no-match results or error conditions, but overall complete for a check tool.

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 covers all parameters. Description adds examples for tool_input and clarifies the default event, going beyond schema documentation.

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?

Clearly states the tool probes hypothetical tool calls against guardrails without execution or audit logging. Distinct from sibling arai_recent_decisions which handles actual firings.

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?

Explicitly advises using before actions that might be regulated to avoid deny-and-retry loops. References sibling tool for actual firings, providing context for when to use.

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