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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds one useful behavioral detail -- that older questions are included in what is returned -- but says nothing about scoping semantics beyond the word 'scoped'.

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 with no filler, and the key scope qualifier ('including older questions') is stated immediately. Minor cost from the compressed, slightly awkward noun stack 'scoped original retained question'.

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?

An output schema exists, so return values need not be described, and annotations cover safety, leaving a low burden. However, for a read tool whose payload is conceptually unusual ('retained question'), the description does not explain what a retained question is or what 'scoped' means for the agent_id, leaving a residual ambiguity.

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%, with both gap_id and agent_id documented (including where the IDs come from), so the baseline is 3. The description's 'scoped' and 'by ID' phrases reinforce the two-parameter lookup but add no meaning beyond the schema.

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 ('Reads') and resource ('scoped original retained question by ID'), which distinguishes it from the plural list siblings such as knowledge_gaps_list. The phrasing 'original retained question' is somewhat jargon-heavy, but the single-record-by-ID purpose is unambiguous.

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 explicit when-to-use guidance or alternatives; it never names knowledge_gaps_list or workspace_knowledge_gaps as the way to obtain a gap_id. The only routing hints live in the input schema's parameter descriptions, not in the description itself.

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