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

With no annotations at all, the description carries the full burden and does so well: it discloses the live on-chain read, the exact output categories, the delegate-type classification scheme (plain wallet vs known program like Jupiter/Raydium/Orca vs unknown), and even the $0.005 cost. It stops short of explicitly stating the operation is read-only/no-side-effects or noting latency/rate limits, which is the only remaining gap.

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?

Purpose and scope are front-loaded in the opening clause, and the cost note is a compact closer. The first sentence is long and heavily parenthetical, but the parentheticals (approvals analogy, program examples) genuinely aid an agent's routing decision rather than padding.

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 and no annotations, so the description must cover both behavior and returns — it does, enumerating result categories, the risk-level summary, revoke guidance, and pricing. An agent has enough to decide and call it correctly without further context.

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?

Only one parameter exists and schema description coverage is 0% — the schema gives just a regex pattern with no textual description. The description implies the input is a Solana wallet address ('Check a Solana wallet's ... delegates') but never names or explains the address argument, its base58 format, or whether non-wallet addresses are accepted.

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 — checking a Solana wallet's live SPL and Token-2022 delegates — and enumerates exactly what the result contains (delegate, allowance, UNLIMITED flag, delegate classification, permanent delegate, close authorities, risk level, revoke guidance). This is clearly distinguishable from siblings like solana_token_check or solana_address_lookup, which cover broader token/address inspection.

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 framing ('Solana's version of token approvals, the way drainers move funds') implies the security-audit use case, but the description never explicitly says when to pick this over solana_token_check or solana_address_lookup, nor does it state any preconditions (e.g. the wallet must be on Solana mainnet). Usage is inferable rather than stated.

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