get_decision

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns a dict or error if not found, and lists output keys. It implies a read-only operation without side effects. However, it does not mention permissions, rate limits, or idempotency, which are minor omissions for a simple getter.

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 extremely concise—3 sentences that front-load the main action and return format. The structured 'Returns' section adds clarity without extra words. Every sentence serves a 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?

The tool has a simple single parameter and an output schema exists, but the description fails to explain the 'decision_id' parameter or the error dict format. No guidance on sibling differentiation is given. For a tool with 0% schema coverage and no annotations, this leaves gaps in understanding.

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 0%, so the description must compensate. It does not define the 'decision_id' parameter (e.g., format, source, uniqueness). The parameter name is self-explanatory, but the description adds no additional 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?

The description explicitly states it returns a single decision with outcome detail or an error dict. The verb 'Return' and resource 'decision+outcome' clearly define the action. The singular form distinguishes it from the sibling 'get_decisions'.

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 use when a specific decision is needed, but it does not explicitly state when to use this tool over alternatives like 'get_decisions'. No 'when not to use' or comparison criteria are provided, leaving ambiguity in tool selection.

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