so_get_question

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

With no annotations, the description carries the full transparency burden. The word 'Fetch' clearly signals a read-only lookup, and the ID format explanation adds useful context. However, it does not disclose response shape, error behavior, or limitations beyond the basic operation.

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 two short sentences with no filler, front-loading the action and resource. It earns its place by adding a concrete example and the exact ID format in a compact way.

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 lookup-by-ID tool, the description plus schema sufficiently explain the required parameter and the primary output (body). Minor gaps remain such as not listing other returned fields nor describing the site default, but the tool's atomic purpose is adequately covered.

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?

The input schema already provides full descriptions for both parameters, so the baseline is 3. The description adds an illustrative ID example and ties the ID to the Stack Exchange URL, which reinforces the schema semantics but does not significantly extend them.

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 clear verb ('Fetch') and a specific resource ('full question detail (with body)'), distinguishing the tool from siblings by its question-ID scope and emphasis on the body. The example and URL pattern further pinpoint exactly what the tool operates on.

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 implies the tool should be used when you have a question ID and need the full question body, but it does not explicitly state when not to use it or how it differs from siblings like so_get_post or so_get_answers. That comparison is left to the model to infer.

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