decision_lineage

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

Annotations are absent, so the description must compensate, but it only states the basic action. It does not disclose read-only nature, permissions, empty chain handling, or ordering implications beyond 'oldest-to-newest'.

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?

Single sentence that efficiently conveys the core functionality. Front-loaded with action and scope, no filler.

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?

For a simple read tool with one parameter and an output schema, the description covers the main idea but lacks parameter explanation and context about the chain structure. Adequate but incomplete.

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?

The parameter 'uuid' has 0% schema description coverage. The description mentions 'a decision' but does not clarify that uuid identifies the decision, nor does it specify format or constraints. Minimal added meaning.

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 'show' and the resource 'supersession chain' for a decision. It distinguishes the tool from siblings like 'current_decision' (shows current only) and 'supersede_decision' (creates a supersession), making the lineage intent unique.

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?

No guidance on when to use this tool versus alternatives such as 'why', 'current_decision', or 'supersede_decision'. There is no explicit context for selection or exclusion.

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