get_registered_models

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

Annotations already indicate readOnlyHint=true, confirming a safe read operation. The description adds the 'all' scope but does not disclose any behavioral traits like pagination, sorting, or performance implications. For a tool with no parameters and an output schema, the description is adequate but could provide more context about the response structure or limitations.

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 a single, clear sentence with no extraneous information. It effectively conveys the tool's purpose without wasting 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?

Given the tool's simplicity (no parameters, no nested objects, output schema present), the description is sufficiently complete. It covers the core functionality of listing all registered models, and the output schema can define the return format.

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, so the description inherently covers the parameter semantics by implying no input is needed. Schema description coverage is 100% (no params to describe). The description adds no additional parameter meaning because none exists, which is appropriate.

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 clearly states the action ('List all registered models') and the resource ('in the model registry'). It uses a specific verb and identifies the exact scope, effectively distinguishing it from sibling tools like get_registered_model (single model) or search_logged_models (different search criteria).

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 provides no guidance on when to use this tool versus alternatives. It does not mention that this tool returns all models without filtering, whereas siblings like search_logged_models or get_registered_model might be more appropriate for specific lookups. An explicit 'when to use' note would improve decision-making.

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