metaculus_project_questions

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

With no annotations provided, the description carries full behavioral burden. It discloses that the data is 'credential-free' and 'normalized', indicating a read-only operation from a public source. However, it lacks details on rate limits, pagination behavior, data freshness, or error handling (e.g., invalid slug).

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 description is two sentences: first sentence names the resource, second sentence adds context (credential-free, normalized rows). Every word is informative with no fluff. It is appropriately front-loaded.

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?

Given the tool's simplicity (2 parameters, no output schema, no annotations), the description provides a basic level of completeness. It explains the source and normalization but omits output format details, default slug behavior, and any limitations. Could be enhanced with minimal additions.

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 clear definitions: 'limit' (integer, default 10, max 25) and 'slug' (string, required). The description adds no additional meaning beyond the schema—it simply states the tool's overall purpose. Baseline score of 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 description clearly states it returns 'Metaculus question rows from a credential-free public project feed page.' It specifies the action (returns), resource (Metaculus project questions), and context (public project feed), distinguishing it from sibling tools like metaculus_questions (all questions) and metaculus_category_questions (category-specific).

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?

The description implies usage for fetching questions from a specific project via the required 'slug' parameter. However, it provides no explicit guidance on when to choose this tool over alternatives (e.g., metaculus_questions for global feed, metaculus_category_questions for categories). No when-not or exclusion criteria are mentioned.

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