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

With no annotations, the description carries the burden, and it does add one genuine behavioral fact beyond the schema: totals are returned alongside results so an empty result can be distinguished from an empty corpus. However, it omits other useful traits such as read-only confirmation, ordering, and how the limit interacts with pagination.

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 tightly written sentences that are front-loaded with the definition of scope and end with the practically relevant empty-vs-empty-corpus note. No filler; only slight compression loss from the list-like first clause.

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?

There is no output schema, and the description only partially covers the return shape (it mentions totals but not result structure). For a query tool with no annotations and an undocumented limit parameter, it is adequate but leaves ordering, result fields, and pagination behavior unaddressed.

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 inside the schema (attribution, validation, principal ownership), while limit has no description anywhere. The description adds nothing about parameters, so it does not compensate for the undocumented limit parameter.

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 precisely defines the resource scope it returns: open questions nobody has addressed, untested hypotheses, and hypotheses tested exactly once. That is specific and lets an agent understand the concept quickly, though the retrieval verb is only implied by the name and it never names a sibling to distinguish itself from.

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 explicit when-to-use or when-not-to-use guidance and no reference to alternatives among the many methodist_* siblings. The intent (find gaps to work on) is inferable, but nothing tells the agent what condition should select this tool over methodist_get_current_dose, methodist_find, or methodist_hypotheses_for_question.

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