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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds genuinely non-obvious context beyond that: the derivation is deterministic and chain-independent ('the same on every chain'), which tells the agent results can be cached and reused across chains. It stops short of describing the return shape or deployment assumptions.

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?

Two tight sentences with the core behavior front-loaded and the determinism property as a supporting clause. No wasted words or hedging.

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?

For a one-parameter read tool, the description covers what is computed but not what is returned (a bare address versus an object), and there is no output schema to fill that gap. It is adequate but leaves the agent guessing about the response shape.

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 0% and the single 'eoa' property has no description, so the description carries the burden. It does clarify that the input is an EOA (as opposed to the derived SCA), which is a meaningful distinction, but gives no format guidance (hex vs checksummed address) or validation expectations.

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 verb ('Derive') and a specific resource ('the smart contract account (SCA) that holds Loopr positions'), plus the input it derives from (an EOA). This is clearly distinguishable from siblings such as get_positions or get_strategy, which read state rather than derive an address.

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?

Usage is only implied: the agent can infer this is the lookup to perform when it needs the SCA address before calling position or build/quote tools. There is no explicit when-to-use statement, no mention of alternatives, and no note on error behavior for EOAs without a deployed account.

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