fanar_list_models

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

No annotations are provided, so the description carries the full disclosure burden. It does add genuinely non-obvious context — entitlements vary per key and some models (Fanar-Sadiq-2) must be enabled by Fanar — but it says nothing about the return shape, ordering, or whether the list can change over time, which matters for a discovery endpoint with no output schema.

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 sentences, front-loaded with the core action, followed by the one caveat an agent actually needs. Nothing is padded or redundant.

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 zero-parameter discovery tool with no annotations or output schema, the definition covers the essential question (which models are callable by this key) and the key gotcha (per-key entitlements). The only shortfall is that it never hints at what the returned list contains, which the absent output schema would otherwise have to carry.

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 the schema-side baseline is 4. The description appropriately adds no parameter detail because there is nothing to parameterize, and correctly frames the scoping as implicit via the API key rather than a request field.

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 a specific verb and resource ('List the Fanar models this API key may call') with an explicit scoping qualifier ('this API key'), which is unambiguous against discovery-style siblings like fanar_chat or fanar_validate_quotations. The mention of Fanar-Sadiq-2 powering the quotation validator and deep research further situates it relative to the other tools.

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?

Usage is only implied: the entitlement note hints you call this to discover what your key can access, but there is no explicit when-to-use, when-not-to-use, or named alternative. No prerequisites (e.g., must be called before choosing a model) are spelled out.

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