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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds that it makes exactly one upstream call and returns the provider response unmodified with unprocessed snapshots, which is useful behavioral context, but it says nothing about pagination behavior, rate limits, or data volume (the limit/days caps live only in the schema).

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?

Three short sentences, front-loaded with the core purpose and the single-endpoint constraint, with no filler. The opening "Token Account History." merely repeats the title and is the only wasted fragment.

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 a full output schema and 100% parameter coverage, the description needs only to frame purpose and routing, which it does adequately. What is missing is differentiation from get-wallet-token-balance-history and any note on the 30-day/1000-entry caps that shape how the tool is called in practice.

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 100% and every parameter (days, page, limit, sortByAsc/Desc, vybeTokenFilter, ownerAddress) is documented in the schema itself. The description adds no parameter meaning beyond restating the endpoint path parameter, so the baseline 3 applies.

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?

"Fetching raw wallet token account history with unprocessed balance snapshots" gives a specific verb and resource, and the endpoint mapping (GET /v4/wallets/{ownerAddress}/token-accounts-balance-ts) pins down the exact scope. It does not explicitly distinguish itself from the very similar sibling get-wallet-token-balance-history, so an agent has to infer the difference from the words "raw" and "unprocessed".

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?

"For custom time series analysis and advanced processing" implies when this tool is appropriate, but there are no explicit exclusions and no named alternative for the common case (e.g. "use get-wallet-token-balance-history for processed/summarized balances"). Usage is only implied.

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