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 structurally. The description adds nothing beyond that: no note on pagination, result ordering, or what a project row contains, so it contributes essentially zero behavioral context.

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?

The single noun-phrase fragment is not so much concise as under-specified; it has no verb and no front-loaded statement of action. It is short, but the brevity reflects missing content rather than efficient structure.

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?

The tool is simple and has an output schema plus annotations, so return-format detail is not required. However, the complete absence of differentiation from metaculus_tournament_questions and metaculus_category_questions leaves a real selection gap for the agent.

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%: slug documents format, examples, and 404 behavior, and limit documents the default and maximum. Per the high-coverage baseline the schema carries the burden, and the description adds nothing further, so a 3 is appropriate.

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 phrase 'Metaculus project question rows' names a resource but supplies no verb and largely restates the tool name. It does not distinguish this tool from its near-identical siblings metaculus_tournament_questions and metaculus_category_questions, so an agent cannot tell which scoping applies without opening the schemas.

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, no prerequisites, and no mention of the alternative question-list tools (tournament/category variants) despite three such siblings existing. The agent is left to infer everything from the name.

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