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

No annotations are provided, so the description carries the full burden. It usefully declares the operation read-only and points elsewhere for generation, but says nothing about auth needs, rate limits, pagination, or whether the catalog is static or dynamic. Adequate but thin for a tool with zero annotation coverage.

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?

Two short sentences, no filler, with the core purpose front-loaded and the read-only/generation caveat following. Every clause earns its place.

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 one-parameter list tool this is close to sufficient, but with no output schema the description never indicates what a result looks like (fields, model IDs, pagination). Adding one clause about the returned shape would close the remaining gap.

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% and the single 'kind' parameter already documents its enum and default, so the schema does the work. The description's mention of 'image and video models' loosely mirrors the filter but adds no format or behavioral detail beyond it, so this is the baseline 3.

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 Tyndall AI image and video models'), which is enough for an agent to tell it apart from get_pricing and list_capabilities. It stops short of explicitly naming or contrasting those siblings, so it lands at a clear-but-undifferentiated 4.

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?

It does give some routing context ('Read-only catalog; generation is on https://www.tyndallai.com'), which steers the agent away from expecting generation here. However, it never states when to choose this over list_capabilities or get_pricing, nor any prerequisites, so usage is only implied.

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