get_decision_detail

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

No annotations provided, so description carries full burden. It discloses the return fields (rationale, context, etc.) and the 'found: false' case. It implies higher cost than recall surfaces, adding valuable behavioral context. Lacks explicit read-only statement but 'get' implies it.

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?

Description is concise, well-structured, and front-loaded. First sentence states purpose, followed by usage guidance, input list, and return details. No waste—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?

Given no output schema, description fully explains return values. It covers purpose, usage, parameters (key one detailed), return fields, and error case. For a simple read tool with moderate complexity, it is complete.

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 has 100% description coverage, baseline 3. Description adds important context for decisionId (source from recall result), which surpasses baseline. Other params are not elaborated in description but are clear in 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?

The description explicitly states 'Expand one decision to its full detail' with a specific verb and resource. It distinguishes from sibling tools by contrasting with recall surfaces that return summaries only.

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 clearly states when to use this tool (after getting summaries from recall surfaces) and when not to (when summary suffices). It names specific alternative tools (get_relevant_context, get_project_decisions, get_session_decisions).

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