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

readOnlyHint=true already declares the safety profile, so the description's 'Read-only' line largely restates it. It does add value by pointing to the portal/CLI lanes for edits and by previewing the response contents (capability and default/enabled flags), which is useful context beyond the annotation. No pagination or scoping behavior is mentioned.

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?

Front-loaded with the resource identity, then the field inventory, then the use cases, then the read-only boundary. The field enumeration is dense but justified since no output schema exists. Minor redundancy in restating read-only against the annotation.

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?

With no output schema and no parameters, the description carries the whole burden and does so: it lists the returned fields, states when to use it, and clarifies that mutation is out of scope. An agent has everything needed to select and call it.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is empty and 100% covered trivially.

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?

Names a specific resource (the organisation's AI model catalog) with an explicit verb framing and enumerates the exact fields returned (key, tier, context window, output limit, capability flags, enabled/default). The CLI equivalence note (`ankra ai models list`) and the contrast with the editing lanes make it unmistakable against neighbors like get_ai_settings or get_ai_environment.

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?

Gives concrete trigger scenarios: answering 'which models can I use' and diagnosing why a model cannot run tools. It also states the boundary that catalog edits happen via portal or CLI rather than this tool. It stops short of naming a sibling alternative to use instead for adjacent questions, so it is clear context without full when-not routing.

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