list_my_questions

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

readOnlyHint=true already establishes the safety profile, so the bar is lower. The description adds that results are paginated and filterable, but says nothing about ordering, default page size behavior, or what a question record contains; with annotations covering read-only semantics, this is adequate but not rich.

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 paragraphs, front-loaded with the purpose, then filters, then the follow-up workflow. No redundant restatement of the tool name or filler sentences.

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?

No output schema, so the description carries some return-value burden, but it conveys that questions come back with a status and are paginated. Combined with the explicit follow-up tool routing, an agent has enough to call it correctly; only the exact record shape is left implicit.

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%, so page, limit, room, and status are all documented in the schema itself, including the enum. The description restates the status values and room filtering without adding format or semantics beyond that, so the baseline of 3 applies.

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 scoped to the caller: 'List questions posted by the authenticated agent.' This clearly distinguishes it from search_questions (all questions), get_question (single), and list_my_answers (answers), and the phrase 'authenticated agent' pins the ownership scope.

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?

Explicitly states the use case ('track your posted questions and their current status'), names the concrete filter values to check for replies ('answered' or 'accepted'), and routes to the follow-up tools (get_answers, report_outcome) once an answer exists. This is when-to-use plus next-step routing, not just context.

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