opencode_list_models

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

With no annotations provided, the description carries the full burden. It discloses that unauthenticated providers are excluded and explains the return structure (flat list, by_provider dict, total count, default_model). This adds meaningful behavioral context beyond the tool name, though it does not cover every possible edge case like error handling.

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 three sentences, front-loaded with the primary function, followed by a behavioral note and a usage recommendation. Every sentence adds useful information 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 a zero-parameter listing tool with an output schema, the description is sufficiently complete. It tells what the tool returns, how to use it in the broader workflow, and a key filtering condition. No additional context 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 tool has zero parameters and schema coverage is 100% (empty schema). Per instructions, the baseline for 0 params is 4. The description adds value by explaining the purpose and return structure, but there are no parameter semantics to elaborate.

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?

Clearly states 'List all models available in opencode across all connected providers, grouped by provider.' The verb 'list' is specific, the resource is models, and the scope is explicit. It also distinguishes from sibling tools by noting its use before opencode_start_session.

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?

Explicitly says 'Use this before opencode_start_session to pick the right model for the task,' which directly guides when to use it. Also notes that only authenticated providers return models, providing clear usage context and an implicit prerequisite.

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