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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context beyond them: ownership is resolved with ownerOf at call time rather than assumed, and the tool is keyless and cannot sign or move anything. It does not cover edge behavior (e.g. what is returned when an address holds no position), which keeps it from a 5.

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 core purpose is front-loaded in the first sentence, which is good. But the closing clause repeats itself — "Free, keyless, read-only — it cannot sign or move anything. Cost and signer: free and keyless, nothing to sign" says the same thing twice, and the parenthetical asides make the prose denser than needed.

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 an output schema present, the description needn't explain return values, and annotations cover the safety profile; the description fills in the live-resolution and keyless-auth context. The remaining gap is behavioral edge cases (no position found, invalid token ID), which an agent would want before calling.

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 parameters are already documented, including the omit-to-use-our-position behavior. The description reinforces the address-omission semantics but says nothing about tokenIds or how tokenIds interacts with a supplied address, so it adds little beyond the schema baseline.

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?

States a specific resource (a veHYDX voting-escrow position on Base) and enumerates exactly what is returned: live owner, voting power, locked HYDX, unlockability, plus the separate oHYDX option token. It explicitly disambiguates veHYDX from oHYDX and, by framing itself as a position read, distinguishes itself from siblings like hydrex_votes and hydrex_claimable.

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?

Gives concrete invocation guidance: "Works for any Hydrex holder: pass an address, or omit it to read the position this server operates." That resolves the main ambiguity of the optional parameters. However, it never names an alternative tool or states when a sibling (e.g. hydrex_votes) would be the better choice, so it stops short of full routing guidance.

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