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. The description adds nothing beyond that: no note on ordering, whether rows are paginated, what the limit interacts with, or whether an unknown slug errors or returns empty. With annotations carrying the safety profile, the description contributes no behavioral context at all.

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 short, but this is under-specification rather than conciseness: a single sentence fragment that omits the operation entirely. Brevity here costs the agent information rather than saving it, so the terseness does not earn 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 there are only two parameters. Still, for a list endpoint in a dense family of Metaculus question tools, the description should at minimum state that it lists questions belonging to a category slug; it does not, leaving the core intent unstated.

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%, with both 'slug' and 'limit' (default 10, max 25) documented in the schema, so the baseline is 3. The description adds no meaning about slug format, category hierarchy, or row ordering beyond what the schema already states.

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 essentially a restatement of the tool name in noun-phrase form: 'Metaculus category question rows' for 'metaculus_category_questions'. It contains no verb and never says what operation is performed (list/retrieve rows), so an agent cannot tell what the tool actually does beyond the name. The word 'category' does hint at scope relative to metaculus_project_questions and metaculus_tournament_questions, but that distinction is already carried by the name itself.

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 many sibling question tools (metaculus_questions, metaculus_project_questions, metaculus_tournament_questions, metaculus_question). No conditions, prerequisites, or alternatives are stated. The agent must infer usage entirely from the name.

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