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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that it returns open positions and the specific fields, which is useful but doesn't disclose additional behavioral traits like pagination, ordering, or whether the address can be an EOA or deposit wallet (though the schema mentions 'owner EOA or Deposit Wallet'). No contradiction with annotations.

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 sentence that front-loads the resource ('Open positions of a Polymarket trading account or its owner address') and then lists the returned fields. No wasted words.

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 simple read-only tool with one parameter and no output schema, the description is mostly complete. It names the key return fields and the accepted address types. It could mention whether positions are filtered by market status or if there is pagination, but given the simplicity and annotations, this is a minor gap.

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 the schema already documents the single 'address' parameter. The description adds that the address can be an owner EOA or Deposit Wallet, which is a small semantic addition beyond the schema's '0x address (owner EOA or Deposit Wallet)'. Baseline 3 is appropriate.

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 the tool returns open positions of a Polymarket trading account or owner address, and lists the key fields (size, average price, current price, value, P&L). It uses a specific verb ('Get') and resource ('positions of a wallet'), which is clear. It doesn't explicitly differentiate from siblings, but no sibling appears to overlap directly with positions.

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 description implies the tool is for reading positions for a given address, and the schema requires an address. It doesn't explicitly state when to use this tool versus alternatives, but the context is clear enough: it's the only positions-related tool among siblings. No exclusions or alternative routing are provided.

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