get_question

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

With no annotations, the description carries the disclosure burden. 'Fetch' implies a read-only retrieval, and 'with all its answers' discloses the scope of the returned data. However, it does not mention behavior for invalid ids, answer ordering, or whether any additional data is included, leaving some 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?

A single, front-loaded sentence that states the core operation and return scope with no filler. Every word contributes meaning.

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 simple single-id getter, the description covers what is fetched and what is included. Its main omission is the absence of an explicit return-value shape or error behavior, but no output schema exists and the tool's complexity is low.

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 0%, so the description must help interpret the id parameter. It indirectly identifies id as the question identifier through 'Fetch one question', but it adds no explicit parameter details such as value semantics or behavior for missing/invalid ids.

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 uses a specific verb ('Fetch') and resource ('one question'), and further clarifies that the result includes all answers. This distinguishes it from list_questions (plural listing) and ask_question/answer_question without ambiguity.

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 phrase 'one question' establishes clear context: use this to retrieve a single question by id rather than listing questions. It does not explicitly name alternatives or exclusions, but the single-item fetch context is evident and non-misleading.

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