list_question_entries

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

Annotations already establish this as a safe read-only operation, and the description is consistent with that. However, the description adds little behavioral context beyond the annotations—no mention of defaults, filter combination semantics, or return shape, though the output schema covers part of that gap.

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 a single, front-loaded sentence with zero filler. Every word contributes to identifying the operation and resource.

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 read-only list/search tool, the description plus a fully documented schema, safe annotations, and an output schema is nearly complete. It loses a point only because it gives no hint about how to choose among the many related question and mastery-path siblings.

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% for all 9 parameters, so the schema carries the semantic load. The description adds only the generic idea of search/filter and does not elaborate on any parameter beyond what the schema already states.

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 names a specific action ('Search and filter') and a specific resource ('DeepTutor's native Question Bank'), making the collection-level intent unmistakable. It is clearly distinct from single-entry siblings like get_question_entry and from category listing tools like list_question_categories.

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 no guidance on when to use this tool instead of get_question_entry, list_question_categories, or other question-related tools. There are no stated exclusions or conditions, so the agent must infer usage from the tool name and schema.

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