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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds significant context: the provider_incident block, unreliable limits during provider incidents, and extended creditData. No contradiction with annotations.

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 (3 sentences) with no redundancy. It front-loads the primary purpose, then parameter details, then behavioral warnings. Every sentence provides necessary information.

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 1-parameter tool with no output schema, the description covers the key aspects: purpose, parameter usage, response shape, and an important edge case (provider incident). It could be more detailed about the full return fields, but given the simplicity, it is fairly complete.

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 description must compensate. It specifies the array length constraint (1-50) and the batch response shape ($results, errors$), which are not in the schema. It also implies each item is an account ID. This adds meaningful guidance, though the exact meaning of each element could be more explicit.

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 specifies the verb 'Returns' and the resource 'full account objects including extended creditData'. It also mentions the HTTP endpoint and the batch shape, clearly distinguishing it from similar tools like openfinance_list_accounts.

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 explains how to pass account_ids (array, 1-50) and the response shape, but does not explicitly state when to use this tool over alternatives like openfinance_list_accounts or openfinance_get_account_balance. Usage context is implied but not consolidated.

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