get_decision

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

No annotations exist, so the description must bear the full burden. It only says 'Sync lookup', indicating a synchronous read, but does not disclose if it returns full detail, side effects, permissions, or error conditions. Essential behavioral traits are missing.

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 a single, concise sentence: 'v2.1.0 — Sync lookup by DecisionId.' Every word is necessary; there is no fluff. It is front-loaded and efficiently conveys the purpose.

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 the tool's simplicity (one parameter, no output schema), the description is minimally complete. It explains what it does but lacks details about the return value. For a sync lookup, users might expect description of the result object, which is absent.

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%, so the schema already documents the id parameter. The description adds no extra meaning beyond 'DecisionId', which is a repetition. Baseline 3 is appropriate as it doesn't enrich 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?

The description clearly states it's a sync lookup by DecisionId, specifying the verb 'lookup' and resource 'Decision'. This distinguishes it from sibling tools like list_decisions (list all) or find_decisions_by_context (search by context).

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 usage when you have a specific DecisionId, but provides no explicit guidance on when not to use it or which alternative (e.g., list_decisions, find_decisions_by_context) to prefer. With many sibling tools, lacking usage distinctions is a gap.

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