list_models

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a modest amount of context by noting the list is scoped to models 'this server allows access to', hinting at permission-based visibility, but says nothing about pagination, ordering, or default limit behavior.

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 tight sentence with the scope constraint front-loaded. No wasted words, though it is arguably too terse for a tool with an undocumented parameter.

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 read-only list tool with no output schema and only two optional params, the description is minimally adequate. The undocumented 'limit' parameter and absent mention of result ordering or pagination leave small but real 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 only 50% – the 'limit' parameter has no description in either the schema or the description. The description's 'optionally filtered' weakly gestures at the filter param without explaining matching semantics beyond what the schema already says ('Substring of the model name'), so it does not compensate for the coverage gap.

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 (List) and resource (models) with a scope qualifier ('this server allows access to'). However, it does not distinguish itself from siblings like model_info, get_model_fields, or name_search, which an agent could plausibly confuse with a model-listing tool.

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 filtered' implies the filter parameter is available but gives no guidance on when to use this tool versus model_info, get_model_fields, or search_count. No alternatives, prerequisites, or exclusions are named.

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