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

With no annotations, the description carries the full burden. It does add real context: the data source (Polymarket), the scoring methodology (skill-weighted money versus market odds via x402Pulse), and a scope disclaimer ('Data, not trading advice'). It says nothing about refresh cadence, pagination, geographic coverage, or response shape, so the disclosure is partial rather than complete.

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 the resource identification front-loaded and the disclaimer kept to a short trailing clause. The parenthetical explaining the 'skilled-trader lean' metric is dense but earns its place by defining a non-obvious term; otherwise there is little waste.

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 single-optional-parameter tool with no output schema and no annotations, the description covers what the data is, where it comes from, and how the skill signal is computed. It stops short of describing the return structure or result volume, which is a modest but real gap given the absence of an output schema.

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 description coverage is 100% and the single optional 'limit' parameter is self-explanatory ('1 to 10'). The description adds nothing about the parameter, so the baseline 3 applies — the schema does the work here.

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 states a clear resource — oil prediction markets on Polymarket covering oil prices, OPEC, Strait of Hormuz and fuel — plus the distinguishing payload (skilled-trader lean from x402Pulse). That content-level specificity separates it from siblings like oil_prices, oil_positioning, and oil_supply, though it never names a sibling explicitly.

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?

There is no explicit when-to-use or when-not-to-use statement, nor any named alternative. The closest thing to guidance is the implied framing that this is market-odds data with a trader-skill overlay rather than raw price data, which a careful agent can use to route, but the description leaves that inference to the reader.

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