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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the four phase values, the scoring-range rule ('closer than Polymarket when the top end is below 0'), that forecasts appear in their minute, that they may not count and why, and that format=concise drops the forecast rows. Pagination behavior when many forecasts exist is not disclosed, which keeps it from a 5.

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 content is front-loaded and the most important payload list comes first, which is good. But the body is one very long comma-chained sentence plus an aside, which makes it hard for an agent to parse the distinct capabilities. Several clauses ('what it still needs', 'your next locks', 'the next steps') overlap and could be tightened.

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?

An output schema exists, so return values needn't be re-explained, and the description still gives a thorough inventory of what the payload contains plus the phase and scoring semantics. The main omission is paging: a cursor parameter exists but the description never says results are paginated or when to follow nextCursor.

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 the schema already documents show, cursor, and the concise format. The description's 'format concise leaves out the forecast rows' essentially restates the schema's own wording. Baseline 3 is appropriate since the schema does the heavy lifting and the description adds little parameter-specific meaning.

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?

States a specific verb+resource ('your forecasting-contest entry') and then enumerates exactly what comes back: phase, score with range vs Polymarket, what's still needed, forecasts left today, next locks, and every forecast with Polymarket's price. This is clearly distinguishable from the general problee_contest and problee_get_forecaster_record siblings.

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 establishes the 'one call for my own entry' use case and explicitly routes the agent to a different tool (problee_create_watch with the forecast_scored trigger) when the goal is notification rather than a snapshot. It also explains the format=concise branch. It falls short of 5 because it never states when NOT to use it in favor of problee_get_question_forecasts or problee_get_scoring_record.

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