close_decision

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

The description discloses that the tool locks the decision from further votes and records the outcome, which are key behavioral traits. However, without annotations, it does not cover permissions, idempotency, or side effects beyond basic locking.

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 highly concise, front-loaded with the main purpose, and uses a clear bulleted list for arguments. Every sentence adds value without 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 no output schema and no annotations, the description covers the tool's purpose, parameters, and side effect (locking). It lacks details on return value or error handling, but is adequate for a simple mutation.

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?

With 0% schema description coverage, the description adds crucial meaning: decision_id is the decision to close, final_decision is optional and uses consensus if empty. This compensates for the schema gap.

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 tool closes a decision and records the final outcome, using specific verbs and resources. It distinguishes from siblings like cast_vote and create_decision by focusing on the closure action.

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 usage when concluding a decision, but lacks explicit when-to-use or when-not-to-use guidance compared to alternatives. The mention of final_decision being optional hints at usage but does not fully specify conditions.

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