get_trending_markets

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. The verb 'Return' indicates a read-only operation, which is helpful, but the description does not disclose any additional behavioral traits such as pagination, output format, or any authorization requirements. It is adequate but minimal.

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 a single, clear sentence with no wasted words. It front-loads the core purpose and is perfectly concise for the tool's simplicity.

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?

The description adequately conveys the main purpose, and the output schema exists to handle return value details. However, it lacks guidance on the optional 'limit' parameter and does not explain how 'top' is defined beyond volume. Given the tool's simplicity, it is mostly complete but not fully self-sufficient.

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 input schema has one parameter 'limit' with a default of 10 and no description. The tool description does not mention the parameter at all, leaving the agent to infer its meaning from the name alone. Since schema description coverage is 0%, the description was expected to compensate but does not.

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's function: 'Return top Polymarket markets by 24-hour volume.' It uses a specific verb ('Return'), identifies the resource ('Polymarket markets'), and defines the scope ('top by 24-hour volume'), which distinguishes it from sibling tools like search_markets and get_market_details.

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?

Usage is implied: the tool is for retrieving trending markets based on volume. However, there is no explicit guidance on when to use it versus alternatives, nor any exclusions or prerequisites. The description does not mention that this is for discovering top markets, and no sibling tool comparison is provided.

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