Permisos pendientes OpenCode

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

No annotations are provided, so the description carries the full burden. It indicates a read-only query operation via 'consulta' and mentions 'eventos recientes', but it does not disclose potential side effects, authentication requirements, rate limits, or what happens when no permissions are pending.

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 that front-loads the action and includes the purpose. Every word earns its place, with no unnecessary repetition 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 a simple query tool with one optional parameter and no output schema, the description provides sufficient context to understand its use. However, it could be improved by clarifying the relationship with opencode_respond_permission and what 'eventos recientes' includes.

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 has 100% coverage with a clear description for the 'directory' parameter, explaining when it may be omitted. The tool description adds no additional semantic meaning beyond the schema, so baseline 3 applies.

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 queries pending permission requests and recent events, with a specific purpose to resolve headless session pauses. It differentiates from siblings like opencode_respond_permission by focusing on querying rather than responding.

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 provides clear context: use this when needing to resolve pauses in a headless session. However, it does not explicitly exclude alternatives or mention when to use other tools like opencode_status or opencode_wait, and no comparison to opencode_respond_permission is given.

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