list_models

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 discloses the read-only nature ('List'), the scope ('downloaded'), and the key output detail ('active one marked'). This is sufficient for a zero-parameter list operation where no destructive or side-effect behavior exists.

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?

A single, front-loaded sentence with no wasted words. It states exactly what the tool does and adds one useful detail about the active model marker.

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?

Given the zero-parameter simplicity and the presence of an output schema, the description is fully complete. It covers the tool's purpose and output nuance with no gaps.

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 the schema reflects that with empty properties. The description correctly omits parameter details; baseline 4 applies as no parameter explanation is needed.

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' with a clear resource: 'MacWhisper's downloaded transcription models'. The parenthetical '(active one marked)' adds distinguishing detail, separating it from sibling tools like list_clips or status.

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 tool's use is self-evident: listing models. There is no explicit alternative or exclusion, but the description implies clear context—if you need to see downloaded models, this is the tool. No competing sibling tool covers this function, so additional guidance is unnecessary.

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