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

With readOnlyHint=true already covering the safety profile, the description adds meaningful context: it discloses the authentication requirement and, for the detail action, explains that endpoint configurations come back with a `parameters` JSON Schema plus a raw UI `config` array. No rate limits or failure modes are mentioned, but for a read-only discovery tool this is solid.

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 core purpose, then an action list, then the return-shape note and auth requirement. Every sentence earns its place; the only nit is the leading whitespace/indentation artifacts and slightly dense action line.

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?

For a read-only 11-parameter discovery tool with no output schema, the description covers purpose, all action modes, auth, and the return structure for the most complex action (detail). Pagination behavior and default handling beyond the schema are not restated, but nothing critical is missing.

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 100%, so every parameter (sort, tags, feature, model_id, per_page, provider, base_model, etc.) is already documented with its applicable action. The description adds no syntax, format, or default details beyond that, so the baseline of 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?

States specific verbs (search and discover) plus the resource (AI models on ModelsLab) and enumerates the five action modes, so an agent knows exactly what the tool covers. Siblings (agent-auth, agent-billing, agent-usage, etc.) occupy entirely different domains, so no sibling confusion arises.

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?

Each action is briefly defined (search/filters/tags/providers/detail) and the parentheticals indicate which parameters apply where. It never explicitly states when to prefer one action over another or what disqualifies a call, but the action inventory gives clear context for selection.

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