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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by warning about the provider_incident block and unreliable data during incidents, which goes beyond the annotations. No contradictions.

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?

The description is concise at three sentences, front-loaded with the primary purpose, then parameter details, then crucial warning. Every sentence provides essential information with no unnecessary words.

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?

Given no output schema, the description fully covers the parameter semantics, response shape (including batch structure and provider_incident edge case), and usage constraints. It is complete for a read-only batch retrieval tool with complex reliability considerations.

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?

With 0% schema description coverage, the description fully compensates: it explains the account_ids parameter is an array of 1-50 strings, describes the batch request shape (implicitly mapping to GET /accounts/:id), and details the response format {results, errors} and special provider_incident block.

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 clearly states the tool returns full account objects with extended creditData, and specifies the verb 'Returns' and resource 'account objects'. It distinguishes from siblings like openfinance_list_accounts by indicating it retrieves detailed objects per ID batch.

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?

The description provides clear usage guidance: pass account_ids as an array (1–50), describes the batch shape {results, errors}, and warns about provider_incident block when values may be unreliable. However, it does not explicitly compare to alternatives like openfinance_list_accounts, so it loses a point for not stating when to prefer this tool.

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