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

No annotations are provided, so the description carries the full behavioral burden. It does disclose genuinely useful non-obvious behavior: the tool is paid via x402 v2 on Base Mainnet with tiered pricing ($12.00 full report, $3.50 signal-only), an optional 0.15% SLA, and a 5%-10% rescue split — cost and payment mechanics an agent must know before invoking. It does not disclose what the forensic report contains, how long the analysis takes, or what happens when invariant checks fail, so the disclosure is real but 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 definition is a single run-on sentence whose latter two-thirds is a pricing/payment parenthetical crammed with dollar figures, SLA percentages, and chain identifiers. The actual capability statement is front-loaded, but the signal is drowned by commercial boilerplate that does not help the 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?

This is a complex, paid, multi-file analysis tool with 5 parameters, no annotations, and no output schema. The description should explain what the dossier and invariant engine actually produce, how the PROCEED/ABORT verdict is determined, and what the rescue-split path entails, but it covers only price and payment rail. Given the complexity, the coverage is thin beyond billing mechanics.

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 100%, so every parameter including nested name/code fields is already documented in structured form. The description adds no parameter-level meaning — it never mentions contracts, protocolName, tvlTargetUsd, ownerTreasury, or contractAddress — so the baseline 3 applies.

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 resource ('Multi-Contract DeFi Protocol Dossier & Invariant Engine') and a concrete outcome ('deterministic PROCEED/ABORT signal & forensic report'), which is more than a tautology. However, it is buried under pricing boilerplate and never distinguishes itself from siblings like ingravity_auditSolidityContract or ingravity_simulateDeepExploitAndWhitehatBounty, so an agent cannot tell which audit tool applies to a given request.

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 named alternative. The word 'Multi-Contract' weakly implies this is for protocols spanning 1-20 files rather than single contracts, but the agent must infer that routing rule entirely on its own.

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