Listar modelos

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

There are no annotations, so the description has to carry the behavioral disclosure. It does convey a read-only inventory action over the local catalog, which is useful context, but it does not disclose filtering behavior, return format, pagination, or what happens when the catalog is empty.

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?

This is a short, front-loaded, single-sentence description that uses no filler and adds value over repeating the title. Every word earns its place in conveying the local catalog scope.

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?

The description fully communicates the core listing behavior, but the absence of annotations, output schema, and parameter documentation leaves meaningful gaps around the 'provider' filter and the exact shape of returned model profiles. For a simple list tool, this is only partially complete.

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 schema describes the 'provider' parameter only as a string and the description never mentions it at all, despite 0% schema description coverage The agent has no guidance on whether 'provider' filters, which values it accepts, or what effect it has on the result.

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 ('Lista'), the target resource ('perfis de modelos'), and the scope ('catálogo local'). This differentiates it from the sibling tools, which recommend, compare, and explain rather than list.

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 implies when it should be used: when an agent needs to enumerate model profiles from the local catalog. However, it does not explicitly compare alternatives or state when not to use this tool, leaving the routing decision to inference.

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