record_decision

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

The description outlines basic behavior (recording proposals and responses) but fails to disclose side effects, storage, or permissions. With no annotations, the description should carry this burden but only partially does.

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, concise sentence that efficiently communicates the tool's purpose with no unnecessary words.

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 seven parameters (including nested objects), two required, no output schema, and no annotations, the one-sentence description is insufficient. It omits critical details about parameter usage and tool behavior.

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 coverage is 0%, meaning no parameter information is provided in the description. The description mentions agent proposal and human response but does not map them to parameters or explain required fields like session_id and decision_type.

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's purpose: recording a decision trace with agent proposal and human response. It uses a specific verb and resource, distinguishing it from sibling tools like record_correction or record_event.

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 explicit guidance on when to use this tool versus alternatives such as record_correction. The description does not mention prerequisites or scenarios where this tool is appropriate or not.

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