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

Annotations only declare the generic profile (non-read-only, open-world, idempotent, non-destructive); the description adds the substantive behavior: the first call deploys a deposit wallet and returns actions[], each typed_data must be signed by the AGENT wallet via EIP-712 in order, ClobAuth links the CLOB account, the approvals batch grants buy/sell/collect rights, and signatures must be returned within 10 minutes. It also explicitly reassures 'Nothing here moves money', which is the key behavioral fact for a signing flow.

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 purpose is front-loaded and every clause (gasless, live-only, venue_allowlist, two-call flow, 10-minute window, no money movement) carries operational weight. The dense parenthetical explanations of ClobAuth and approvals are slightly compressed but still readable.

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?

There is no output schema, and the description compensates by describing what the first call returns (actions[] containing typed_data to sign) and what the second call produces, plus the failure-relevant time constraint. Nothing an agent needs to execute the two-step activation correctly appears to be missing.

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 100% and the schema already defines signatures as 'one 0x… signature per action, in order' and activation_id as 'Second call only'. The description's parameter information largely restates this (second call takes activation_id + signatures, in order), so it adds little beyond the structured fields beyond reinforcing the ordering constraint.

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 opens with a specific verb and resource ('Enable prediction markets') plus a one-time/gasless qualifier, and the surrounding text makes clear it is the setup step distinct from siblings such as place_prediction_order, get_predictions_account and list_prediction_markets. An agent can identify the tool's role without opening the schema.

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?

It states the prerequisites (venue_allowlist must contain 'polymarket', live-only trading, no paper simulation) and spells out the two-call sequence with a 10-minute window, which is strong when-to-use guidance. It does not explicitly route the agent away from any sibling (e.g., get_predictions_account as a status check), leaving that to inference.

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