aa_get_model

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

Discloses partial matching and behavior on multiple matches (returns candidates). No annotations provided, so description carries full burden; it does so adequately but lacks mention of read-only status.

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?

Description is concise with clear sections (Args, Returns). No unnecessary words, and layout helps parsing.

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?

Tool has output schema, description covers return value (full model details or candidates). Single parameter, context is fully addressed.

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?

Single parameter 'identifier' is explained beyond schema (UUID, slug, name; partial matching supported). Schema coverage is 0%, so description adds essential semantics.

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?

Description clearly states the tool retrieves detailed info about a single LLM model by identifier. It distinguishes from sibling tools like aa_list_llms (list all models) and aa_compare_models (compare models).

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?

Description implies usage for fetching details of one model but does not explicitly contrast with siblings or state when not to use. No exclusion or alternative guidance.

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