list_order

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

No annotations provided, so description carries full burden. It states it is a 'limit sell order', implying execution only at specified price, but does not elaborate on order lifecycle, partial fills, or failure conditions. Some behavioral context is added, but not comprehensive.

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 sentences with no wasted words. The first sentence states the action, the second provides critical context. Efficient and front-loaded.

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?

No output schema is present, so the agent has no idea what the tool returns. The description does not mention return values, side effects, prerequisites (e.g., holding shares), or error conditions. This is a significant gap for a mutation tool.

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% with all parameter descriptions present. The description adds minimal extra meaning beyond the schema, only clarifying the 'limit' nature which relates to price. Since schema already documents parameters well, rating is baseline 3.

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 it places a limit sell order on a prediction market outcome, using specific verb+resource. It distinguishes itself from any AMM sell by declaring there is no AMM sell, making the purpose unambiguous.

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 explicitly says 'This is the ONLY way to sell prediction market shares', giving clear context for when to use. However, it does not list explicit alternatives or when-not-to-use scenarios, though the exclusivity implies its singular role.

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