list_markets

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the core operation and does not mention read-only behavior, pagination, ordering, possible empty results, or whether the engine parameter accepts a specific format beyond the schema default.

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?

A single, front-loaded sentence with no filler. It starts with the action verb, names the resource, and states the scope in an efficient way.

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 tool with one optional parameter and no output schema, the one-sentence description combined with the schema is largely sufficient to understand what the tool does and how to invoke it. It could be more complete with an explicit note about what a 'market' is or what the returned data looks like, but those are minor given the tool's low complexity.

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% for the single 'engine' parameter, including a default value, so the baseline is 3. The description adds no parameter details beyond what the schema already states, but it does align naturally with the 'engine' field.

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 uses a specific verb ('List'), a clear resource ('markets'), and a scoping constraint ('for a given trading engine'). It distinguishes itself from list_engines by operating on markets rather than engines, though it does not explicitly differentiate from sibling list_boards.

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 phrase 'available for a given trading engine' implies the tool is used when a caller already has an engine and needs its markets. However, there is no explicit guidance about when to choose this tool over alternatives such as list_boards or list_engines, and no exclusions are mentioned.

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