get_market_by_slug

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

No annotations are provided, and the description does not disclose behavioral traits beyond stating it 'gets detailed information'. It does not mention whether the operation is read-only, any authentication requirements, rate limits, or what 'detailed information' entails. This leaves significant ambiguity for an agent.

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 two sentences with no extraneous words. The purpose is stated upfront, and the additional clarification about the slug is concise. Every sentence serves a clear function.

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 parameter and no output schema, the description is adequate but not complete. It does not specify what fields or structure the 'detailed information' includes, which could be important for an agent to understand the return value without additional context.

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?

The schema covers 100% of parameters with a description of the slug. The tool description adds value by explaining that the slug can be extracted from the Polymarket URL, which supplements the schema and aids agents in constructing the correct input.

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 the verb 'Get' and the resource 'detailed information about a specific market by its slug identifier'. It also explains how to obtain the slug from a Polymarket URL, making the purpose unambiguous. This distinguishes it from siblings like list_active_markets or search_markets.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention when not to use it, nor does it reference sibling tools like search_markets or get_event_by_slug. The only hint is that the slug comes from a URL, but no comparative context.

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