mcode_models

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: it starts no task and may report zero models even when a default model is configured, which prevents misinterpretation of results.

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 tight sentences with no filler. The first sentence states the mechanism, the second states the purpose, and the third states a critical caveat. Every sentence earns its place and key information is front-loaded.

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 list tool with one optional parameter, no output schema, and annotations covering safety, the description is complete. It tells the agent what command is run, how to use the result, that no task is started, and how to interpret an empty result from OAuth providers.

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 100% for the single optional `search` parameter, so the schema already documents its meaning. The description does not add parameter-level detail, but it also does not need to; the baseline of 3 applies because the schema carries the param semantics.

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 states a specific action ('List what this MiniMax Code installation reports via `mcode provider list --json`') and clear resource (models). It also distinguishes itself from siblings by explicitly saying it is used to pick a `model` value for `mcode` / `mcode_reply`, and clarifies that it 'Starts no task.'

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 gives clear usage context: use this tool to select a `model` value for `mcode` / `mcode_reply`. It also provides a useful exclusion ('Starts no task') and a caveat about official OAuth providers listing zero models. It does not explicitly name sibling alternatives, but the intended use is well established.

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