Euler V2 Vault & EVC Sub-Account Auditor

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without the description. Beyond that the description says nothing behavioral: no mention of RPC/network dependency and possible latency despite openWorldHint, no failure modes for invalid vault addresses, and no indication of what a default invocation (no parameters) returns. It is pure 'when to use' text with zero behavioral disclosure added.

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?

It is a single front-loaded sentence that wastes no words, and the trigger condition comes first. The dense list of protocol jargon (EVK, IRM kink, EVC XOR bitmaps) makes it hard to parse quickly, which keeps it below 5.

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?

With three optional parameters, no output schema and an open-world read tool, the description adequately conveys the high-level outputs (decoded caps, simulated slippage, inspected bitmaps). However, it omits chain scope, what the response shape looks like given there is no output schema, and any indication of behavior when optional inputs are omitted.

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%, and the schema already explains vaultAddress defaults, accountAddress scanning prefixes 0..3, and simBorrowDelta units and default. The description adds no parameter meaning beyond that, so the baseline of 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 four specific capabilities tied to a concrete protocol: auditing an Euler V2 (EVK) vault, decoding uint16 compact floating-point caps, simulating Euler IRM borrow kink slippage, and inspecting EVC 256-bit XOR sub-account bitmaps. This is far more specific than the title and clearly separates it from siblings like simulate_morpho_blue_kink_slippage or unpack_fluid_liquidity_layer_state by protocol and data structure. It falls short of 5 only because it never explicitly contrasts itself with those siblings.

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?

The opening 'Use this tool when a user wants to...' supplies explicit trigger conditions across four scenarios, so an agent can match user intent to the tool. It does not state when NOT to use it, list prerequisites such as requiring a mainnet RPC connection, or point to alternative tools for non-Euler protocols.

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