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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds real interpretive context the annotations cannot: what the phase values mean, how to read the score range ('closer than Polymarket when the top end is below 0'), and that unresolved forecasts include a why-not-counts reason. It stops short of describing pagination behavior despite the cursor parameter.

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?

Purpose is front-loaded in the opening clause and every sentence carries information (payload contents, format trade-off, watch alternative). The main weakness is the long run-on middle sentence enumerating many fields, which is dense but not padded.

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 zero-required-parameter read tool with an output schema and full annotation coverage, this is largely complete: it explains the phases, the score-range interpretation, and the notification alternative. The only omission is pagination guidance for the cursor, which matters because the tool can return many forecast rows.

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% and each parameter already carries its own description, so the schema does the heavy lifting. The description reinforces the 'format concise' behavior but says nothing about the 'show' enum (all/open/resolved) or how cursor paging interacts with the forecast rows, so it adds limited meaning beyond the schema.

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 opens with a specific verb+resource ('Your forecasting-contest entry in one call') and enumerates the payload (phase, score with range, forecasts left, next locks, per-forecast Polymarket comparison). The possessive 'your' scopes it to the caller's own entry, which partially separates it from siblings like kellian_contest or kellian_get_scoring_record, but no sibling is named for contrast.

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 gives one explicit routing rule ('To be told when a forecast is scored, create a watch ... with the forecast_scored trigger') and explains that 'format concise leaves out the forecast rows'. However, there is no guidance on when to prefer this over kellian_contest, kellian_get_scoring_record, or kellian_get_question_forecasts, so the agent must infer the boundary.

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