opencode_models

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds 'discovered verified' which gives some context about the scope of the list, but it does not elaborate on what 'discovered' means, whether this reflects live state, or any other behavioral nuances beyond the annotations.

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, front-loaded sentence with no wasted words. It clearly states the action and object, achieving maximum conciseness without under-specifying the core purpose.

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?

There is no output schema, so the description should explain what the tool returns and how parameters affect the result. It does not describe the return format, whether the list is complete or filtered by default, or the meaning of 'discovered verified.' This leaves a significant gap in an agent's understanding.

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%, and the description provides no information about the parameters (tier, modality, provider, availability). The description fails to compensate for the lack of schema documentation, leaving the agent to guess whether these are filters, required fields, or what values they accept.

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 uses the specific verb 'List' and clearly identifies the resource as 'discovered verified OpenCode models.' It distinguishes the tool from siblings like opencode_delegate and opencode_status, which perform different actions on models.

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 implies usage for listing models, but provides no explicit guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The sibling tools are clearly different in function, so the need for this tool is implicitly clear, but explicit guidance is absent.

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