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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds substantially more: the data source (NearBlocks indexer), the exact fields returned, the auth model ('no API key required', optional x-credit-token header), the price ($0.02/call over x402 on Base) and the rate limit (1 free call/day). That is behavioral context well beyond the structured fields.

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 hook question and provenance framing are front-loaded and the required input/pricing are sequenced sensibly. It is slightly padded with marketing-style boilerplate ('new != malicious', 'Not financial advice') that does not help invocation.

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 one-parameter read tool with an output schema, everything an agent needs is present: what it returns, where the data comes from, how to authenticate, cost and rate limits, and how it relates to sibling tools.

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?

There is a single parameter with 100% schema coverage, and the description only restates it as 'Required input: account'. It adds no format, semantics or constraints beyond what the schema already documents, 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?

The description names a specific verb+resource - returning the PROVENANCE (creation date, creator, deletion status) of a NEAR account - and explicitly contrasts it with the sibling near_account ('near-account gives the current state; this gives the PROVENANCE'). An agent can distinguish the two without opening either 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?

It states the triggering context ('Before you trust, pay or copy a NEAR account'), names the alternative it is not (near_account) and the one it pairs with (near-wallet-activity). This is explicit when-to-use plus sibling routing.

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