oracle_run

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

The description mentions caching behavior and that results are returned when unchanged. However, it does not clarify whether these commands have side effects, require specific permissions, or what happens on cache miss. Given no annotations, this is insufficient.

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 concise sentences effectively communicate the core functionality. No unnecessary words; front-loaded with the action.

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?

The description covers caching and return behavior, but misses details on execution when cache is outdated, error handling, and command constraints. Given the presence of an output schema, some missing context is acceptable, but more is needed.

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 single parameter 'commands' has no schema description (0% coverage), and the description only adds that commands must be 'allowlisted'. It does not explain the format, constraints, or example values, leaving ambiguity.

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 the tool runs allowlisted commands through a cache layer and returns cached results when unchanged. This distinguishes it from sibling tools like oracle_read or oracle_ask, but 'allowlisted commands' could be more specific.

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?

No explicit guidance on when to use this tool versus alternatives like oracle_ask or oracle_grep. The description implies it is for executing commands, but lacks context for proper selection.

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