list_enabled_models

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

With no annotations, the description carries the full burden. 'List' implies a read operation and the optional restriction is disclosed, but there is no mention of return format, pagination, or what 'enabled' means operationally. For a trivial list tool this is adequate but thin.

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 sentence that front-loads the action and the optional qualifier, with no wasted words.

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 two-optional-param list tool with no annotations and no output schema, the description covers the main behavior but omits the 'purpose' parameter entirely and gives no hint of the returned shape, leaving modest 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?

Schema coverage is 100%, so both parameters are already documented, giving a baseline of 3. The description adds 'restricted to a given set of model names' for model_names, but says nothing about the 'purpose' parameter or its use/configure enum.

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?

States a specific verb and resource ('List enabled models'), and the 'enabled' qualifier distinguishes it from the sibling list_models and list_model_providers. However, it does not explicitly name those siblings or clarify the boundary, so an agent still has to infer which list tool to pick.

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 phrase 'optionally restricted to a given set of model names' implies a filtering use case, so usage is somewhat implied. But there is no explicit when-to-use guidance versus list_models or list_enabled_providers, nor any stated prerequisites.

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