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, but the description adds nothing on top of that. It doesn't mention pagination behavior, ordering, or what a 'row' contains, and there is no context an agent couldn't get from the annotations and schema alone.

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?

It is three words long, which is terse but not concise in a useful sense - this is under-specification, not economy of language. A sentence fragment that omits the verb and any scope information doesn't earn its brevity.

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 explained, and the two parameters are covered by the schema. However, for a tool sitting among four near-identical Metaculus question listers, the description leaves the core selection question completely unanswered, which is inadequate for this sibling density.

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%: 'limit' (default 10, max 25) and 'topic' (optional Metaculus feed topic slug) are both fully documented in the schema. The description adds nothing beyond that, 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?

The description 'Metaculus question rows' is a noun fragment that restates the tool name rather than stating a verb+resource action. It gives no clue how it differs from the many sibling question-listing tools (metaculus_category_questions, metaculus_project_questions, metaculus_tournament_questions, metaculus_question), leaving an agent unable to tell which one to pick.

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 when-to-use guidance at all: nothing says whether this is the general feed lister and the category/project/tournament variants are the filtered ones. The 'topic' parameter hints at filtering, but no condition or alternative is named, so the routing decision is entirely left to inference.

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