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

With no annotations, the description carries the full burden, and it does disclose real behavior: data is read live from Base, the feeRecipient and owner are read from the contract, verification comes from Sourcify, and verdicts carry two-sided flags (MISMATCH, matches true/false, creator_traded not_traced, milestone hit/burned/pending with an 'n' on every verdict). It implicitly establishes a read-only call. It stops short of stating failure modes, RPC/rate-limit behavior, or what happens for an unknown symbol.

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?

It is a single comma-spliced run-on that heaps a dozen clauses into one sentence, so nothing is front-loaded beyond the opening framing and scanning the capability list is hard work. Nearly every clause does carry distinct information, which keeps it out of the 1-2 range, but a bulleted or clause-separated structure would earn the content far more.

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 no output schema and no annotations, the description must encode the return surface, and it names most of it: creator/platform fee wallets, owner, timelock and scheduled upgrades, verification links, creator allocation unlock conditions, graduation liquidity/LP lock, volume, per-wallet net flows, block-pinned balance check, fee reconciliation, and milestone log. What is missing is the response shape (field names, nesting) and error/edge behavior for unknown or non-AgentPad tokens.

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 coverage is 100% and the single 'token' parameter is documented as a symbol or 0x address, so the schema already does the work. The description adds nothing about the parameter itself (e.g., symbol-vs-address resolution or ambiguity), leaving baseline 3 appropriate for a one-param tool.

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 opening clause 'Where the money goes for an AgentPad token, read live from Base' states a specific resource and read scope, and the enumeration that follows narrows it to fee routing, ownership, upgrades and liquidity. It is identifiable apart from get_token and list_tokens, though the overlap with the honest_volume sibling for volume data is never acknowledged.

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?

There is no statement of when to reach for this tool versus agentpad_info, get_token, or the dedicated honest_volume tool, even though it duplicates volume and net-flow content those siblings cover. The agent must infer from the ingredient list that this is the comprehensive transparency/due-diligence call.

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