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

The description adds meaningful context by stating the tool is paid ($0.03 USDC) and that it consolidates multiple checks in one call. However, with readOnlyHint=false there is no disclosure of side effects, payment flow, or failure behavior; the cost warning is helpful but the behavioral profile is incomplete.

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?

The description is two short sentences with no filler. The cost, one-call promise, and output categories are all front-loaded and each element adds value.

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?

The description gives a useful high-level picture of what the tool returns and that it costs money, which helps an agent decide whether to call it. But it lacks guidance on how to provide the required contract, what chain means, and how the payment_signature flow works, and there is no output schema to fill those gaps.

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% (payment_signature only), and the description does not explain the semantics of chain or contract parameters. It lists output categories rather than input meaning, so it only partially compensates for the undocumented parameters.

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 clearly identifies a token pre-trade check as the resource and lists the specific checks it combines: metadata, price, holder concentration, verification, and sanctions. This is distinct enough from most siblings, though it does not explicitly name a sibling to differentiate from.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative tools are mentioned. The phrase 'pre-trade' implies timing, but the description does not explain how this tool compares to or conflicts with related tools like genesis402_screen_sanctions or genesis402_wallet_brief.

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