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

With no annotations, the description carries full behavioral burden and it delivers: it declares the call is read-only, states cost ($0.01 per call), typical latency (under 2s), and the data categories returned. This goes well beyond a generic 'inspect wallet' phrasing.

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 compact: purpose, return contents, use cases, commercial/latency notes, and parameter help are packed into three short sentences plus a one-line parameter explanation. There is no filler or repetition of schema 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 single-parameter read-only tool, the description covers purpose, output fields, use cases, cost, latency, and semantics of the only input. No output schema exists, but the description's list of returned data categories gives the agent an adequate expectation of the result.

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?

The input schema only provides a string property named 'address' with zero description coverage. The tool description compensates fully by labeling that parameter and giving a concrete example address, which is exactly what the agent needs to invoke the tool correctly.

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?

Description identifies a clear action and resource: 'One-call profile of a Solana wallet,' and enumerates exactly what the call returns (SOL balance, SPL holdings, activity, failure rate, age, program flag). This scope distinguishes it from siblings like simulate_transaction or payment_info.

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 gives explicit application contexts: judge a counterparty, monitor a treasury, or research a wallet before interacting with it. It does not explicitly name alternative sibling tools or state when not to use it, but the guidance is sufficient for selection among these distinct siblings.

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