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

Annotations already cover read-only, idempotent, non-destructive, so the description correctly focuses on added context: the '[read]' tag, the notable fact that accounts are usable 'without any key', and a full enumeration of returned fields. Missing pagination/ordering details, but the behavioral picture 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 '[read]' tag and core resource statement; the provider enum list is long but functionally necessary. Dense but no wasted sentences.

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, the description lists return fields (provider, account_id, account_uuid, name, default_model, model_overrides, USD limits) and explains identifier usage, which is what an agent needs to chain into ai_chat. Pagination and ordering remain unspecified, a minor gap for a list tool.

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%, so the description carries the full burden and does: it enumerates all 14 valid provider values and states 'omit for all', fully compensating for the bare string|null schema. An agent can construct the call correctly from the description alone.

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?

The description names a specific resource (the merchant's AI accounts) and scopes it as the accounts ai_chat can run on, which distinguishes it from the many other list_*_accounts siblings. The verb 'list' is only conveyed by the title, but the resource scope is unambiguous.

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?

It explicitly tells the agent what to do next with the results: 'Pass provider + account_id (or account_uuid) to ai_chat,' which is a clear downstream usage instruction. It also explains that omitting provider returns all accounts. No explicit when-not guidance, but the usage context is clear.

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