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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that – no note that a missing slug returns 404, no pagination behavior, no indication of what 'rows' contain, even though the schema mentions the 404. With annotations present the bar is lower, but this adds no value.

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 four-word fragment is not appropriately sized for a tool with two parameters and many similar siblings; it is under-specified rather than concise. Nothing is front-loaded because there is no useful information to front-load.

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 and annotations cover the safety profile, so return values need not be explained. However, the description gives no context about tournament scope or how it differs from the other Metaculus question-listing tools, leaving an agent unable to confidently choose it.

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 description coverage is 100%, so both the slug and limit parameters are fully documented in the schema, including the 404 behavior and the max of 25. The description contributes no additional parameter meaning, so the baseline of 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?

The description is a noun phrase, 'Metaculus tournament question rows', that essentially restates the tool name. It does not state a verb or clarify what is done with the rows, and it does not differentiate from siblings like metaculus_project_questions or metaculus_category_questions.

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?

There is no guidance on when to use this tool versus the sibling metaculus_project_questions, metaculus_category_questions, or metaculus_questions. The agent must infer the distinction from the name alone.

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