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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is clear. The description adds useful behavioral context: the data is 'updated hourly' and contains 'past facts only' with 'no forecast, no advice.' It does not contradict the annotations and fills in freshness and scope information not present in 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 description is compact and front-loads the core purpose ('Token sheet for a pump.fun token') before listing the detailed metrics. The list of metrics is dense but justified by the absence of an output schema. The final caution sentence is brief and useful.

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?

Without an output schema, the description serves as the primary guide to what the tool returns, and it enumerates the key dimensions (buyer counts by time window, creator activity, top-buyer share, migration, volume, wallet-report participation). For a read-only, single-parameter tool this is largely complete, though it does not describe response format or error behavior.

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 required parameter 'token' with 100% schema description coverage ('Solana token (mint) address, base58'). The description mentions 'mint address' but adds no syntactic or format details beyond what the schema already provides. With full schema coverage, the baseline of 3 is appropriate.

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 clearly states it returns a 'Token sheet for a pump.fun token (mint address) observed by BotSharper' and then enumerates the specific metrics included (launch time, buyer counts, creator activity, migration, volume, wallet-report participation). This is a specific resource with a clear scope, though it does not explicitly name sibling alternatives or use a leading verb like 'retrieve'.

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 closing sentence 'Past facts only, updated hourly: no forecast, no advice' implies when this tool is appropriate (retrieving observed historical token facts) and implicitly excludes predictive use. However, it does not explicitly compare to any sibling tool or state prerequisites or exclusions beyond that single line.

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