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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful behavior beyond that by noting the feed is 'credential-free public', telling the agent no auth is required. It does not discuss pagination or freshness, but the output schema covers return shape.

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?

Front-loads the core purpose before the parameter notes and sibling pointer. It is somewhat run-on with the long slug list inline, but every element (allowed slugs, limit bounds, alternative tool) earns its place.

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 need not be explained, and annotations cover safety. The description supplies the one critical missing piece, the valid slug values, making it complete enough to invoke correctly. Naming the sibling tool rounds it out.

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%, so the baseline is 3, but the description adds the enumerated set of allowed category slugs, which the schema lacks (no enum on the slug property). That is genuinely new information essential to calling the tool correctly. The limit note largely repeats 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?

States a specific verb and resource ('Returns normalized Metaculus question rows') plus scope ('from a credential-free public category feed page'). It explicitly distinguishes itself from the sibling metaculus_project_questions, so an agent can route correctly without opening either schema.

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?

Names the alternative tool explicitly ('Use metaculus_project_questions to retrieve metaculus project questions'), which gives clear routing context. It stops short of stating when-not conditions beyond that single contrast, but the category-vs-project distinction plus the allowed slug list gives solid operational guidance.

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