guardrail_check

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

Wih no annotations, the description carries the full burden and does a good job: it discloses that the tool queries Nexus Memory for protection rules, the category and keyword criteria used, and the form of the result. It clearly frames the tool as a check, implying no mutation, though it does not explicitly state side-effect-freeness.

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 descripion is compact and well-structured: purpose first, mechanism second, usage third. Every sentence contributes meaningful information, and the examples are concrete without being verbose.

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?

With no output schema, the descripion gives a sufficient summary of the return verdict (allow/block/override) and the circumstances for invocation. It could be slightly more complete about how 'override' is interpreted and exactly how tool_input is used in path-based checks, but overall it is adequate for an agent to select and call the tool correctly.

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?

The input schema already documents all three parameters with 100% coverage, so the descripion does not need to add parameter-level detail. The description provides useful context about why command/tool_input matter (safety checks on destructive ops) but does not add semantics beyond the 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?

The descripion states a specific verb and resource: check if an action is safe by querying Nexus Memory, and identifies the return verdict (allow/block/override). This is clear and useful, though it does not explicitly distinguish itself from the sibling guardrail_override beyond implying this tool is a pre-execution check.

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?

It explicitly directs usage before destructive operations with concrete examples (rm, drop, kill, overwrite, recreate). This provides clear context for when to call it, but it does not discus when not to use it or name alternatives like guardrail_override.

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