Create Pending Decision

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description's mention of 'record' is consistent. However, the description does not add any behavioral context beyond what annotations provide, such as side effects or return behavior. It is adequate but not enhanced.

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 sentence plus a short usage note, making it extremely concise and front-loaded. Every word serves a purpose with no redundancy.

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 has 6 parameters (1 required) and an output schema, the description sufficiently covers the core action and usage guidance. It does not explain return values, but the output schema fulfills that role. Minor gaps in behavioral transparency are offset by annotations.

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 100%, so the input schema already documents each parameter. The tool description does not add parameter-level details beyond what the schema provides, but it is not required to. The baseline score of 3 applies as the description adds overall context but no new parameter semantics.

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 'Record' and the resource 'unresolved decision', and explicitly distinguishes from 'ordinary TODOs', which are likely the sibling tool create_memory_todo. This provides a specific and helpful purpose.

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 advises using for 'open choices, not ordinary TODOs', providing clear context and exclusion. While it does not explicitly name alternative sibling tools, the distinction is sufficient for an AI agent to infer when to prefer this tool over create_memory_todo.

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