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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that it works for any public 0x address, but repeats read-only and does not add rate-limit, pagination, or dex-selection behavior beyond what the schema and annotations provide.

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 a single, front-loaded sentence that states the resource, lists the key return fields, and notes the read-only/public-address constraint. There is no wasted terminology.

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 rich annotations, full schema description coverage, and an output schema, the description is complete enough for an agent to call the tool correctly. It also proactively lists the snapshot fields, which is useful context even though the output schema exists.

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 both the address and dex parameters are already documented in the schema. The description adds context about the address being public but does not explain the dex parameter or add semantic detail beyond the schema.

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 the resource as a perp account snapshot and enumerates the returned fields: equity, margin usage, withdrawable, and open positions. It does not explicitly differentiate this from sibling tools such as hl_portfolio_risk or hl_whale_positions, so it falls short of the top score for sibling differentiation.

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 phrase 'works for any public 0x address' gives some usage context, implying no authentication is needed for public data. However, it does not state when to use this tool instead of alternatives like hl_portfolio_risk, nor does it describe exclusions or prerequisites.

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