stacks_market_list

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses pagination and mainnet-only availability, but it does not state whether the operation is read-only, whether authentication is required, or what the returned market objects contain.

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 front-loaded with the core purpose, then concisely covers return behavior, filters, and the mainnet constraint. The final tip about earning_opportunities is related but not directly necessary for invoking this tool.

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 listing tool with fully documented input parameters and no output schema, the description is largely complete. It could be improved by explicitly routing agents to search/get alternatives, but the essential context for calling the tool is present.

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 input schema already documents limit, status, category, and featured in detail. The description restates the filtering dimensions but adds no syntax, defaults, or format guidance beyond the schema.

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 states a clear verb and resource: list prediction markets on stacksmarket.app. It is specific about scope and filters, but it does not explicitly distinguish this listing tool from sibling tools such as stacks_market_search or stacks_market_get.

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 usage for paginated browsing with optional status/category/featured filters and notes mainnet availability. However, it does not say when to use this tool instead of stacks_market_search, stacks_market_get, or other market tools, and gives no exclusions.

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