list_models_grouped

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

No annotations provided. The description discloses a 7-day cache, adding transparency about data freshness. However, it omits other behavioral details like authorization or 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?

Two concise sentences: one for purpose, one for caching. No redundant information.

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?

Sufficient for a list tool with simple parameters. Lacks explicit output format but 'grouped into families' implies structure. No output schema needed.

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% with descriptions like 'Brand id.' and 'Category id.' The description adds no further parameter semantics, so baseline 3 applies.

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 tool lists a brand's models grouped into families, with 'heterogeneous' and caching duration. It distinguishes from sibling tools like list_all_models (ungrouped) and list_generations.

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 phrasing 'grouped into families' implies usage when family groupings are needed, but no explicit when-to-use or alternatives (e.g., list_all_models) are provided.

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