explain_decision

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

Describes the behavior of walking the causal-parent chain and returning it in order. No annotations exist, so the description adequately covers the operational behavior, though it could mention whether it is read-only.

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?

Two brief sentences plus a usage example. No wasted words; the key action is front-loaded.

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, the description explains the return structure ('chain in order from the requested event to its root') sufficiently. Could be slightly more explicit about the data format, but overall complete for the tool's complexity.

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?

Adds meaning to the 'event_id' parameter by explaining it as the starting point of the chain. The 'max_depth' parameter is already described in the schema; the description provides context on why depth might be needed.

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 the verb 'walk' and the resource 'causal-parent chain', and specifies the output order. It distinguishes from siblings like 'explain_event' by focusing on the parent chain traversal.

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 gives usage scenarios ('why did this fill happen', 'trace the cause of order 42'), but does not provide explicit when-not-to-use or alternative tools.

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