provider_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 non-destructive read and 'already-linked' discloses a prerequisite, which is useful behavioral context. It does not disclose failure behavior for unlinked providers, whether results are cached/live, or any rate limits.

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?

One front-loaded sentence with zero waste; the verb and scope come first and the constraint follows immediately.

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?

An output schema exists, so return values need no explanation. For a one-parameter read tool, the description supplies the resource, the provider value set, and the linked-account precondition, which is sufficient for correct invocation.

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 0% and the single 'provider' parameter has no enum, so the schema alone leaves the accepted values undefined. The description compensates by naming the valid providers (ChatGPT, Claude, Gemini, Mistral), effectively supplying the missing value set, though it doesn't state exact string casing or format.

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 states a specific verb and resource ('List models') and scopes it to the four named provider accounts. It does not explicitly distinguish itself from siblings like provider_status or triforce_models, but the resource ('models' per provider account) is unambiguous.

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 'already-linked' implies a precondition, so an agent can infer this only works after an account is linked. However, there is no explicit when-to-use guidance, no statement of what to do when no provider is linked, and no routing versus provider_status or triforce_models.

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