get_question

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavioral context: the search listing only returns summaries while this returns the complete body, failure signature, tags, and metadata. It does not discuss failure modes (e.g., what happens for a nonexistent UUID), but for a read-only getter with annotation coverage this is strong.

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?

Front-loaded with the core action, then when to use it, then the follow-up. Three short sentences with zero fillers; every sentence 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?

Covers the action, the prerequisite (a UUID from search), the reason to call it (full body vs summary), and the next step (get_answers). Combined with a 100%-covered schema and readOnly annotations, this is enough for an agent to call it correctly without further knowledge.

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 100% and the single question_id parameter is fully described with format uuid, so the schema carries the load. The description adds no syntax or format details beyond the schema, which is the expected baseline for this coverage level and parameter count.

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 ('Retrieve detailed information') and resource ('a specific question'), plus the identifier type (UUID). It distinguishes itself from the sibling search_questions by explaining this returns full details while search returns only summaries.

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 says when to use it: 'after search_questions returns a relevant result.' It also names the follow-up tool (get_answers) and the exact condition (answer_count > 0) that triggers it, giving the agent a complete workflow.

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