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

Annotations already establish that the tool is read-only, idempotent, open-world, and non-destructive. The description adds useful behavior beyond annotations by stating that results are paginated and by listing the returned order fields. It still does not mention auth needs or rate limits, but with rich annotations the added pagination detail is meaningful.

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 short and front-loaded, starting with the core resource and scope before adding behavior and usage context. The field list is somewhat redundant with the output schema, but it remains efficient overall.

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?

Given a rich annotation set, an output schema, and a moderately documented input schema, the description is mostly complete for a read-only paginated list tool. It covers purpose, read-only behavior, pagination, and returned fields; the main omission is explicit routing guidance versus related sibling tools.

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 only 60%, and the description does little to compensate for the undocumented parameters. It mentions the address requirement and lists 'coin' among returned fields, but does not explain the dex, limit, or offset inputs or how pagination should be controlled beyond saying 'paginated'.

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 states a specific verb and resource: retrieving open resting orders for an address. It also names the fields returned, which helps an agent understand what kind of data this tool exposes. It does not explicitly distinguish itself from nearby siblings such as hl_get_orderbook or hl_get_account, so it falls short of a 5.

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 'Use to inspect any wallet's live order book footprint' provides implied usage context, but there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The agent can infer the basic use case, but routing between this and related orderbook/account tools is left unaddressed.

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