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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered structurally. The description adds the useful boundary that financial changes happen on the website, but says nothing about result size, pagination behavior, or what 'recent' means for top-ups, leaving real behavioral gaps.

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?

A single front-loaded sentence with the capability first and the boundary condition second; no filler, nothing repeated from annotations or schema.

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?

An output schema exists, so return values need no explanation, and the read-only nature is well covered. However, pagination is entirely undocumented and the description doesn't say whether the three sections are always returned together or bounded by the parameters, which is a real gap for a list-bearing 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 description coverage is 0% for the two parameters, so the description carries the full burden and fails: limit and offset are never mentioned. The only hints come from the schema's types, defaults, and min/max bounds; an agent cannot tell from the text that these paginate the top-up list.

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 (Read) plus three concrete resources: coin balance, recent top-ups, and partner status. This cleanly differentiates it from siblings like aimixer_account, aimixer_profile, and aimixer_history, so an agent can pick it without opening the schema.

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 clause 'financial changes use the signed-in website' gives an explicit when-not condition: this tool never mutates billing state, so mutation intents are routed elsewhere. It doesn't name a sibling alternative, but the exclusion is exactly the guidance an agent needs to avoid mis-selecting it for top-ups or payments.

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