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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful behavioral fact: state is DERIVED from support/refute relations and never stored. Beyond that it says nothing about read-only semantics, permissions, or result size/pagination, leaving notable gaps for a tool with zero annotation coverage.

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?

Two compact sentences, front-loaded with the outcome and then the derivation rule. The closing clause ('a claim's status is inside its identity') is more philosophy than operational guidance, but it is short and does explain why state is derived.

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?

For a two-parameter read tool with no output schema and no annotations, the description does explain the return values and their semantics, which is helpful. It still omits question_id format, pagination, and any permission/auth notes, so it is adequate rather than complete.

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 coverage is 50%: run_id is richly documented in the schema itself, while question_id has only a minLength. The description adds marginal meaning by implying question_id must reference an 'open question,' but it does not clarify format or the run-attribution requirement beyond what the schema already provides.

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 states a specific resource (hypotheses addressing a question) and the return payload (each hypothesis's state from a fixed four-value set). It is clear what the tool produces, but it never names or contrasts itself against sibling tools like methodist_hypothesis or methodist_find, so an agent must infer the boundary.

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 phrase 'open question' hints at the triggering context, but there is no explicit when-to-use, when-not, or named alternative among the many methodist_* siblings. The agent is left to infer that this is the lookup for hypotheses tied to a specific question_id.

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