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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the record is 'public' and characterizes the pending-vs-scored split, which is modest extra context; with an output schema present, the return-content detail largely duplicates structured data.

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?

Three compact sentences, front-loaded with the core purpose, followed by content description and usage. Every sentence carries information; no filler or repetition.

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 one-parameter read tool with full schema coverage and an output schema (so return values need not be explained), this covers purpose, content, and invocation timing adequately. The only notable gap is not clarifying its relationship to get_track_record.

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 single forecaster_id is fully documented in the schema. The description reinforces it ('Same forecaster_id you submit with'), tying it to submit_forecast's naming, but adds no format or validation detail beyond that. Baseline 3 applies when the schema does the heavy lifting.

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 and resource ('Get YOUR audited forecast record on VoxOdds') and spells out the two content classes returned (pending receipts and scored Brier results). It references the counterpart write tool submit_forecast, but does not distinguish itself from the similarly named sibling get_track_record, so an agent could still confuse the two.

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?

Gives explicit timing guidance: 'Call this after submit_forecast to confirm your receipts, or any time to check your public track record.' That is clear context for when to invoke it, though it names no exclusion or alternative (e.g., get_track_record) when one of those would be preferred.

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