polymarket_market

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

The description is transparent about the return structure but does not disclose any behavioral traits like idempotency, authentication needs, or rate limits. Since annotations are absent, the description carries the burden, but the simple read operation is adequately described.

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 one sentence stating purpose and a listing of return fields. It is front-loaded and contains no extraneous information.

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 retrieval tool with one parameter, the description is nearly complete: it explains what is returned and the input. Missing information like error conditions or pagination limits, but these are not central given the tool's simplicity.

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 single parameter 'id' is explained as 'Gamma id', which adds meaning beyond the schema's generic type. The description clarifies the identifier's role, though it could specify format or length.

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 tool retrieves 'full detail' for one market by 'Gamma id', and lists the specific fields returned. This distinguishes it from sibling tools like 'polymarket_markets' (plural, for multiple markets) and 'polymarket_clob_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 on when to use this tool versus alternatives (e.g., 'polymarket_markets' for multiple markets, 'polymarket_price' for price only). The description does not mention context or exclusions.

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