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

Beyond the readOnly/openWorld annotations, the description discloses important behavior: the deposit wallet is a Polymarket smart wallet controlled only by the agent wallet, cash is denominated as pUSD equal to USD, deposits from any supported chain land as pUSD within minutes, and pending operations plus the last relayer transaction are included. It does not discuss freshness or caching, but adds substantial context.

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 dense sentence that front-loads the resource and then lists key contents. It is mostly efficient, though the parentheticals and all-caps 'WHERE TO DEPOSIT' make it somewhat run-on.

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 no input parameters and no output schema, the description carries the burden of explaining what is returned. It does so by enumerating account details, deposit instructions, and pending/relayer state, which is sufficient for an agent to know what to expect.

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?

This tool takes zero parameters, so there is no parameter semantics to explain. The baseline for a parameterless tool is 4, and nothing in the description conflicts with that.

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 the caller's predictions account and enumerates the specific contents (deposit wallet, activation steps, pUSD cash, deposit instructions, pending items, last relayer transaction). It is distinguishable from siblings like get_account or get_prediction_positions by its predictions-account focus, though it does not explicitly contrast them.

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 implied by the content: checking activation steps or deposit routes suggests calling this before activating or funding. However, there is no explicit when-to-use guidance or comparison to alternatives such as get_account or activate_predictions.

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