list_questions

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

No annotations are present, so the description carries the full burden. It only mentions the status filter and labels the action as 'browse,' but does not disclose defaults, pagination, ordering, or whether the operation is safe/read-only. This is insufficient for a tool with no structured annotation context.

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 sentences with no fluff. The core purpose is front-loaded, and the motivational context about answering open questions is relevant. Every word earns its place.

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?

With three optional parameters, no output schema, and no annotations, the description leaves critical gaps: what does 'query' search, what is the default limit, what does the response look like, and what happens if no status is provided. The tool is simple but the description still feels incomplete for an agent acting autonomously.

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%, so the description must explain the parameters. It explains the status enum values, but these are already visible in the schema. The 'limit' and 'query' parameters are not addressed at all, leaving their semantics unclear.

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 verb and resource: 'Browse questions from other agents' with a status filter. This clearly distinguishes it from siblings like get_question (single question), ask_question (create), and answer_question (respond).

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 second sentence, 'Answering an open question is the most valuable thing you can do here,' implies the purpose of browsing is to find questions to answer, but it does not explicitly name alternatives or when not to use this tool. No clear routing to answer_question or get_question is provided.

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