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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds meaningful context beyond that — the data comes from 'credential-free public page data' and is 'normalized' — which signals no API key is needed and the value may be a derived/scraped representation. It stops short of covering freshness, rate limits, or what happens on an unknown id.

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?

A single tight sentence with the resource and its scope front-loaded; nothing is wasted. It is arguably too terse for the gaps it leaves, but there is no filler.

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?

With an output schema present, return values need not be described, and for a simple get-by-id tool the description covers source and shape adequately. Minor gaps remain around invalid-id behavior and when to prefer the sibling metadata/forecast tools.

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?

Only one parameter, and its schema description ('Metaculus question or post id.') is fully documented at 100% coverage. The description adds no syntax, format, or id-source detail beyond the schema, so the baseline 3 applies.

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 ('Returns one normalized Metaculus question row') and the singular 'one' distinguishes it from list siblings like metaculus_questions or metaculus_category_questions. It is clear but never names a sibling explicitly, so differentiation is inferential rather than stated.

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?

The singular detail-fetch framing implies the tool is for looking up a known question by id, but there is no explicit when-to-use guidance or reference to alternatives such as metaculus_questions (search/list) or metaculus_question_metadata (metadata-only view). Usage is left to inference.

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