gamma_list_markets

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

Discloses return format (normalized market objects with clob_token_ids for later lookups) and clarifies slug format (not full URL). No annotations, so description carries full burden; adds useful behavioral context beyond schema.

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?

Seven sentences, well-structured with purpose upfront and usage guidelines. Slightly long but every sentence adds value. Could be more concise but not wasteful.

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?

Covers filtering dimensions, slug clarification, and sibling differentiation. Output schema exists, so return details are not needed. Missing some context like pagination behavior, but limit parameter covers that.

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 has high top-level coverage (100% for args), but subparameters lack descriptions. Description only adds meaning for slug parameter ('slug should be...'). Baseline 3 is appropriate.

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?

Clearly states 'List or filter markets when you already have structured constraints.' Distinguishes from search_public (free-text) and get_market_by_slug (single slug). Verb+resource with scope.

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?

Explicitly says when to use (structured filters), when to prefer search_public (free-text) and get_market_by_slug (exact slug). Provides clear alternatives.

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