decide_workflow_improvement_packet

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

Discloses that the decision is immutable and consequential, cannot be overwritten, and requires specific preconditions. This is significant behavioral transparency, especially with no annotations provided.

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 two sentences, concise and to the point, with no redundant or unnecessary information.

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?

While purpose and usage are covered, the lack of parameter explanations and any mention of expected output makes the tool incomplete for correct invocation. An agent would need additional context to populate fields correctly.

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 schema has no parameter descriptions and the description does not explain any of the five fields (decision, evidence, packet_id, rationale, approval_scope). An agent cannot determine what values to provide for each parameter.

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 action: recording an immutable human decision for implementation, publish, or deploy. It is specific about the resource and distinguishes it from sibling tools like approve_task, though it does not explicitly name them.

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?

Provides explicit usage conditions: 'Use only after the user explicitly decides the named scope.' Also states additional requirements for publish/deploy scopes (staging-canary evidence and publish approval for deploy), giving clear guidance on when to invoke.

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