run_taegis_command

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

No annotations are provided, so the description must fully disclose behavior. It states that it runs arbitrary commands and returns raw JSON, which is transparent about the action and output. However, it gives no warning about potential side effects or errors, which would be valuable for an arbitrary-command 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 well-structured with clear sections (overview, Args, Returns). It is front-loaded with the main purpose and every sentence adds value, with no redundancy or filler.

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 an escape-hatch tool, the description covers what it does, how to invoke it, and expected output. It does not mention authentication or error handling, but these are less critical for a generic wrapper and the sibling tools handle specific contexts.

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 description thoroughly explains the 'args' parameter: space-separated CLI arguments after the binary, with a concrete example. Even though schema coverage is 0%, the description fully compensates for this single parameter.

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 runs an arbitrary taegis CLI command and returns JSON output. It explicitly identifies itself as an escape hatch, which distinguishes it from sibling tools that wrap specific searches.

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 says to use it for commands not yet wrapped as dedicated tools, which implies when to use it. It does not explicitly say 'use dedicated tools when available' as an exclusion, but the escape hatch framing provides clear context.

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