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

With no annotations, the description carries the full burden and actually does well: it discloses the auth model (BYOK stored in Secrets under named keys or key_secret), the billing behavior (no markup, provider bills you), and a side effect (every call lands in the run ledger). It omits error/rate-limit behavior and return shape, but the disclosure is above average for an unannotated tool.

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-loads the core purpose, then layers auth, billing and side-effect notes in short clauses. Dense but every clause carries information; slight compression ('[bot-ai]' tag) adds noise.

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 10-parameter tool with no annotations and no output schema, the description covers operational context but leaves most parameters undocumented. An agent can tell what the tool is and how it authenticates, but not what to pass for prompt, messages, system, run_id, max_tokens or temperature.

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 coverage is 0% and only 1 of 10 params has an enum, so the description must compensate. It clarifies key_secret (stored secret name) and indirectly maps Grok/Claude/GPT to the provider values, but leaves bot, prompt vs messages, system, run_id, max_tokens and temperature entirely 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?

States a specific action and resource: a model gateway that calls Grok, Claude or GPT. The verb+resource are unambiguous, but it never contrasts itself against a sibling (there is no competing LLM-call tool, though it references secrets and ledger without positioning against them).

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?

Provides a prerequisite ('Bring your own provider key, stored first in Secrets') which implies when the tool is usable, but gives no explicit when-to-use guidance or alternatives. Usage is inferable rather than stated.

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