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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful trait: results are scoped to what the current account can use. It says nothing about pagination behavior despite limit/offset existing.

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 no filler; the resource and scoping qualifier come first. It is efficient but borders on under-specified rather than tightly packed.

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?

A six-parameter search tool with 0% schema description coverage needs more than one sentence. Pagination, language selection, result-count defaults and the distinction from sibling discovery tools are all missing, though the output schema does relieve it of describing return values.

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 description coverage is 0%, so the description carries the full burden. It only signals three of six parameters (name→query, media type→kind, capability→capabilities) and leaves lang, limit and offset — including all paging semantics and the max of 30 — completely unexplained.

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?

Specific verb (search) plus resource (image/video/audio models) and scope qualifier (current account-available). It implicitly maps to the query, kind and capabilities parameters, but never distinguishes itself from nearby siblings like aimixer_catalog, aimixer_canvas_find_models or aimixer_model_card.

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?

No statement of when to use this versus the many catalog/model discovery siblings (aimixer_catalog, aimixer_canvas_find_models, aimixer_model_card, aimixer_options). The only hint is 'current account-available', which implies entitlement scoping but gives no exclusion or alternative routing.

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