decision_list

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

Description says 'List decisions' implying a read-only operation, but annotation destructiveHint=true suggests mutation. This contradiction undermines transparency. No additional behavioral context beyond what annotations provide.

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 with clear verb, resource, and default. No wasted words. Front-loaded 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?

No output schema, no description of return format or pagination. Contradiction with annotations creates confusion. For a list tool with 3 optional params, more context needed.

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 covers all 3 parameters with descriptions (100% coverage). Description adds default behavior (active decisions) not explicitly in schema, but it's minimal. Baseline 3 appropriate.

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?

Description clearly states verb 'List', resource 'decisions in the local Decision Graph', and default behavior 'Defaults to active decisions', distinguishing from siblings like decision_get (single) or decision_add.

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?

Indicates default behavior (active decisions) but no explicit guidance on when to use this vs alternatives like decision_get or decision_add. Usage is implied from the verb and siblings.

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