Run an advanced remio syscall

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true. The description adds valuable context by warning about 'arbitrary side effects' and the requirement for 'explicit confirmation', which goes beyond the annotations and informs the agent of the risky and user-confirmation-dependent nature of the 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 a single concise sentence, front-loaded with the tool's purpose and followed by the critical safety caveats. Every word earns its place, 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?

Despite being a potentially dangerous and complex syscall runner with no output schema and undocumented parameters, the description provides minimal context beyond the escape-hatch nature and confirmation requirement. It does not explain what a syscall is, what actions/payloads are expected, or what the response looks like, making it inadequate for safe and correct invocation.

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 description coverage is 0%, so the description must compensate by explaining parameters, but it does not mention 'action', 'confirm', or 'payload' at all. The property names are somewhat self-explanatory, but no semantics are added, leaving the agent to guess what values are valid or how they interact.

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 identifies the tool as an escape hatch for running a remio syscall not covered by other sibling tools, which distinguishes it from the more specific tools. The title adds the verb 'Run' and resource 'remio syscall', making the purpose reasonably clear, though 'advanced' and 'not represented above' are somewhat vague.

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 indicates this tool should be used for syscalls 'not represented above', providing a clear when-to-use condition relative to sibling tools. It also states that it 'always requires explicit confirmation', which tells the agent that a confirm parameter must be provided, serving as a usage prerequisite.

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