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

With no annotations present, the description carries the full burden and does well: it discloses the simulation mechanism (state overrides), the exact outputs measured (honeypot flag, transfer tax in bps, liquidity depth), the chain scope (Base Mainnet), and the per-call cost. What is not stated is whether the call is read-only versus partially on-chain, and there is no note on failure or rate-limit behavior.

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 mandatory precondition, then the mechanism and cost in a compact package — every clause carries information. The all-caps opener is louder than necessary but doesn't cost readability.

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 3-parameter tool with no output schema and no annotations, the definition covers purpose, timing, and cost but omits the shape of the return value beyond naming the measured quantities, and says nothing about behavior on unsupported chains or a failed simulation. Adequate to invoke, incomplete for interpreting the result.

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 only 33% — token_address is documented in-schema, while chain_id and simulate_sell are bare. The description partially compensates by scoping everything to 'Base Mainnet', which implies chain_id is effectively fixed at 8453, and 'simulates buy/sell orders' loosely explains simulate_sell. It never states what happens if chain_id is overridden or what simulate_sell=false skips.

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 names a specific action set — simulating buy/sell orders via state overrides to detect honeypots, compute transfer taxes in bps, and verify liquidity depth — which clearly identifies the resource and mechanism. It does not explicitly contrast itself with the siblings check_honeypot or analyze_liquidity, though the 'pre-swap' framing implies this is the umbrella check that supersedes them.

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?

Usage is stated unambiguously: call before any DEX swap or token purchase on Base Mainnet, framed as mandatory. It also discloses the cost (0.005 USDC on Base), which matters for agent planning. It stops short of saying when to prefer this over check_honeypot or analyze_liquidity, so no explicit alternatives are given.

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