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

No annotations are provided, so the description carries the full burden. The verb 'List' strongly implies a read-only operation, and the tool is simple (no parameters). However, it does not disclose any additional behavioral details such as authentication requirements, pagination, or whether the list is static or dynamic. The description is adequate but minimal.

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, well-formed sentence that conveys the complete purpose. No wasted words, no redundant information. It gets straight to the point.

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 tool is a simple, parameterless list operation, and the output schema is present (though not shown in detail). The description provides enough context—'Animica's OpenAI-compatible API'—to clarify the scope. For this level of complexity, the description is complete without needing to elaborate on return values or pagination.

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, and the schema coverage is 100% (trivially). Per the rubric, the baseline for 0 params is 4. The description adds context about what the returned list represents, but there is no parameter-specific semantics to clarify. Baseline 4 is appropriate here.

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 uses the specific verb 'List' and clearly identifies the resource as 'the AI models available on Animica's OpenAI-compatible API.' This is distinct from sibling tools like animica_ai_ask (which asks the model) and animica_ai_job_status (which checks job status). No ambiguity.

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 to use the tool: when one needs to see available AI models. It does not explicitly mention alternatives or exclusions, but the context is clear given the distinguishable sibling names. For a simple listing tool, this is sufficient.

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