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

With no annotations, the description must carry the full behavioral burden, and it does disclose a useful trait: a per-call cost of $0.20 USDC on Base and the fact that checks are aggregated from multiple oracles. It does not say whether the call is read-only, what happens on an unknown or unsupported token, latency, or rate limits.

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?

A single front-loaded sentence with the trigger condition first and no filler. The feature list is dense and slightly comma-spliced, but every clause carries information.

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 is the only source of behavioral detail for a four-parameter, multi-check composite tool. It never describes what the response contains (verdict, scores, flags, mandate result), which is the biggest omission for an agent deciding whether to call it or how to consume 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 75%, so the schema already explains tokenAddress, tradeAmountUsd, and counterpartyAddress. The description only indirectly maps its listed checks onto those parameters ('counterparty KYA' implies counterpartyAddress, 'spend mandate limits' implies tradeAmountUsd) and says nothing about the chain enum or required vs optional fields.

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 concrete composite capability: honeypot audit across multiple oracles, DEX liquidity depth, counterparty KYA, and spend-mandate limits, all in one pre-swap call. It is distinguishable from siblings like aegis_token_audit or aegis_wallet_kya because it is explicitly framed as a bundle, though it never says 'returns' or otherwise pins down the action verb.

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?

'USE WHEN: An autonomous trading agent or sniper bot needs all-in-one pre-swap security' is a clear trigger condition with audience and timing spelled out. It lacks any exclusions or routing advice, so an agent doing only a single check gets no hint to prefer aegis_token_audit or aegis_wallet_kya instead.

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