getSafeBaseTrending

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so the safety profile is covered. The description adds genuinely useful context beyond that: the CanaryGuard zero-honeypot and prompt-injection screening applied to results, plus the 0.02 USDC cost on Base, which signals a paid operation.

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?

Front-loaded with the return content, but bloated by repetition (the token-listing claim appears twice) and a pricing sentence plus an off-scope 'Solana' mention. Several phrases do not earn their place.

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 read-only, two-optional-parameter listing tool with no output schema, the description conveys what is returned, the screening criteria, and the cost, which is largely sufficient. It omits ordering/return-format detail but that is minor here.

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 nominally 100%, so the baseline is 3. The description adds no meaning to 'limit' or 'min_liquidity_usd' beyond the schema (which itself uses boilerplate text), leaving the agent with no added filtering semantics.

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 resource and scope: 'Returns top Base Mainnet tokens by 24h DEX volume and liquidity velocity'. However, the framing 'MANDATORY SECURITY GATE' and the redundant restatement ('Curated Base DEX momentum & liquidity leaders') muddy what is essentially a ranked-token listing tool.

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?

Provides usage contexts, but they are generic and poorly matched to a trending-token tool ('auditing smart contracts, analyzing wallet addresses... on Base or Solana'). No exclusions and no differentiation from siblings like nansenTokenScreener or getTokenHistoryAndSpread, so the agent cannot tell when to prefer this tool.

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