polymarket_homepage_feed

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

The description mentions it's 'credential-free Gamma JSON' and explains differences between feed types (e.g., breaking returns high-movement rows). However, it lacks details on rate limits, data freshness, or whether writes are possible. With no annotations, this is acceptable but not fully transparent.

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 with no wasted words. The key information (purpose, feed enum, differences) is front-loaded. The structure is optimal for an AI agent.

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?

Given no output schema or annotations, the description covers the tool's purpose, parameter details, and feed-specific behavior. It could mention common response fields or pagination behavior, but for a listing tool it is fairly complete.

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 coverage is 100%, but the description adds meaningful context: lists all feed enum values, clarifies that cursor is a keyset from a prior response, and specifies limit defaults and max. This goes beyond the schema's short descriptions.

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 lists Polymarket homepage feed rows and explains the feed enum values. However, it does not explicitly differentiate from sibling tools like polymarket_events or polymarket_markets, making it slightly less distinctive.

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 explicit guidance on when to use this tool versus alternatives among the many Polymarket endpoints. The description implies it's for homepage feeds but doesn't advise when not to use it or mention sibling tools.

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