get_market_info

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

No annotations, but description clearly indicates a read operation (get, returns). It mentions returning full metadata from Gamma API, no side effects hinted. Could mention idempotency or rate limits, but acceptable.

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, each packed with useful information. No fluff. Front-loaded with purpose and immediate action.

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?

Without output schema, description sufficiently explains what is returned (full metadata, specific fields). Mentions key uses, making it complete for an API 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 has 100% coverage with clear descriptions for each parameter. Description adds value by explaining the relationship (conditionId used for other calls) and that either slug or conditionId is sufficient.

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?

States clearly it gets Polymarket market info by slug or condition ID, returns full metadata including description, prices, outcomes, CLOB token IDs. Distinguishes from sibling tools by mentioning conditionId usage for other queries.

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 tells when to use (get market metadata) and what not to use for (CLOB data, OI, resolution), providing alternatives like get_clob_market, get_market_open_interest, get_market_resolution.

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