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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description still adds real behavior beyond that: hourly refresh cadence, a fixed 7-day evidence window, and an explicit 'facts, not advice' disclaimer. It stops short of detail on rate limits or response shape.

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?

Dense but front-loaded: the primary classification comes first, then the secondary 'launch team' signal, then usage, then freshness caveat and disclaimer. Every clause carries information, though the opening 'Protection filter for trading bots' is slightly redundant framing.

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?

There is no output schema, so the description must convey what comes back; it does list the derived facts (serial-creator status, dump frequency, migration count, launch-team behavior) and states the data window and refresh rate. It omits the exact response shape/field names, which is a minor gap for a no-output-schema 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 100% and the schema already documents the single address parameter as a base58 public Solana address for a creator or wallet. The description's mention that the address can be a creator or a wallet mirrors the schema rather than adding new meaning, so 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?

States a specific verb and resource ('tells whether a Solana address is a serial pump.fun creator ... and/or a wallet that repeatedly buys in the launch block'), with concrete qualifying criteria (3+ launches in 7 days, dumps within 5 minutes, migration counts). It is clearly a static-lookup protection filter, distinguishable from the sibling simulation/testing tools (botsharper_simulate_bot, botsharper_test_my_bot).

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?

Gives explicit usage context: 'Check a token's creator before buying.' That tells the agent exactly when to reach for it, but it names no alternative tool or when-not-to-use condition relative to siblings like botsharper_jeton or botsharper_reperes.

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