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

With no annotations, the description carries the full load: it discloses that this is a read operation, documents the default filtering behavior for human tests, and adds a prompt-injection caution about treating answers as third-party content. It omits pagination behavior, result ordering, and any auth or rate-limit context, leaving meaningful gaps.

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?

Three short sentences, zero filler, and the core read purpose is front-loaded before the filtering rule and the safety caution. Every sentence carries information an agent can act on.

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 3-parameter list tool with no annotations, no output schema, and 0% parameter documentation, the description should define what q filters on and how page behaves. The safety and filter notes are good, but the agent is left guessing at the two most operationally important inputs.

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 0% for all three parameters. The description explains the semantics of tests (default exclusion of human tests), but says nothing about q (presumably a search filter) or page (presumably pagination), leaving two of three parameters undocumented anywhere.

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?

States a specific verb and resource ('Read public interviews and participation counts'), which clearly differentiates a list operation from the sibling single-item tools interview_read and interview_preview. It does not explicitly name those siblings, so it stops short of a 5.

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 gives one concrete conditional: human tests are excluded by default and included when tests=true, which is real usage guidance for that flag. It offers no guidance on when to choose this tool over interview_read or interview_preview, so the selection criteria are only implied.

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