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

With no annotations, the description carries the full behavioral burden. It helpfully discloses cost and access ('price $0.01 via x402') and the underlying HTTP endpoint, which are genuine behavioral facts. However it omits rate limits, pagination, and whether the paid call is idempotent/cacheable.

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 bracketed HTTP/price/docs metadata is front-loaded and useful, but the first two sentences restate the same idea twice ('Upcoming entertainment event resolutions' vs 'Upcoming entertainment market resolutions...'). Tighter prose would eliminate the redundancy without losing 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?

There is no output schema and no annotations, so the description must carry more. It does convey the return shape by reference ('Same shape as /v1/calendar') and points to docs, but leaves both parameters and any output/pagination behavior unexplained for a paid, schema-undocumented tool.

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 0% and the description never mentions the required 'days' parameter or the 'category' enum. It says results are 'in date order' but never explains that 'days' bounds the forward window, and it is silent on why a category parameter exists on an already entertainment-filtered endpoint.

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 specific verb+resource ('upcoming entertainment market resolutions in date order with current blended probabilities') and differentiates itself by noting it is 'pre-filtered to entertainment markets' and shares the shape of /v1/calendar. The opening sentence ('Upcoming entertainment event resolutions') is somewhat tautological with the tool name, but the second sentence carries real distinguishing content.

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?

It implies the use case ('the forward calendar of entertainment events an agent can position around') and its relationship to the generic calendar, but never explicitly states when to prefer this over probability_calendar or the many sibling probability_calendar_* variants. Notably it does not address that the schema's own 'category' enum can also select entertainment, leaving the choice ambiguous.

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