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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: no statement of what evidence is returned, whether scenarios are independent, cost/latency, or what 'unmasking' produces operationally.

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?

One sprawling run-on sentence saturated with marketing-style numerics and capitalized slogans. It is not front-loaded with the core action, and much of the length (dates, dollar figures, 'in 34 Flicks') does not help an agent decide or invoke.

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, single-enum audit tool with no output schema, the description should clarify what results (findings, verdicts, evidence) come back and how scenario selection changes them. Neither is addressed, so an agent cannot predict the response shape at all.

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 coverage is 0% for a single required enum parameter with seven values. The description gestures at four of them (omnibus 164%, 10,240-wallet sybil, cross-chain 218%, Goldman PB) but never maps prose to the literal enum tokens, and leaves ALL, PERP_ORACLE_REFLEXIVE_TRAP, and LAW0_SOVEREIGN_COPYABLE_LOCK completely unexplained.

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 does convey a specific verb+resource in domain terms: it audits tokenized equity over-total float and unmasks sybil wallets under 'Law 0'. However, the intent is buried under dense narrative ('34 Flicks', '$2.6B Retail Semi Inflow'), and there is no plain-language statement of what an invocation returns, so an agent must decode jargon to grasp the purpose.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of how this differs from siblings such as affine_shield6_finance_bogle_audit or the combined bogle+energy tool. The agent must infer from the name that this covers tokenized equity/13F sybil scenarios only.

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