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 contributes nothing further — no mention of what the feed contains, whether topic scoping changes results, ordering, or feed freshness. It adds no behavioral value beyond the structured fields.

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?

At five words it is technically compact, but this is under-specification rather than conciseness — nothing is front-loaded because nothing is said. A short fragment that leaves the agent uninformed does not earn credit for 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-value explanation is not required. However, for a tool surrounded by many Metaculus siblings, the description is too thin to guide correct selection or invocation, leaving the agent with the name alone.

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 slug) are both fully documented in the schema. The description adds no parameter meaning, so the baseline of 3 applies — the schema does all the work here.

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 comments feed question rows' largely restates the tool name and adds only a vague noun phrase ('question rows'). It does not clarify what a 'feed' returns or how it differs from siblings such as metaculus_top_comments, metaculus_question, or metaculus_questions, so an agent cannot confidently distinguish it from those tools.

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 statement of when to use this tool versus the many sibling comment/question tools. No prerequisites, no exclusions, no alternative routing is given. Usage must be inferred 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.