authorize_docker_optimization_session

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

The description discloses meaningful behavioral traits beyond annotations: it stores a process-local secret, permits only fixed paths/recipe/modes/budgets, and explicitly enumerates actions it does not perform. This is strong transparency for an authorization tool, although it does not directly address the destructiveHint annotation or revocation behavior.

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?

Two front-loaded sentences with no filler. Every clause earns its place: the action and scope come first, followed by side-effect and boundary details. The negative action list is dense but highly useful for safe invocation.

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?

The description is strong on behavioral boundaries and side effects, and an output schema exists so return values need not be covered. However, it omits parameter semantics and usage context, which are necessary for an agent to confidently invoke this tool correctly in a workflow surrounded by many similar authorization and optimization tools.

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 0%, so the description carries the burden of explaining parameters. It does not explain preview_id, preview_content_sha256, authorization_summary_sha256, or the authorization constant beyond their names. An agent gets no additional meaning from the description to fill these required parameters correctly.

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 states a specific verb ('Authorize'), a specific resource ('exact Docker optimization Preview'), and a one-time scope ('once'). The negative boundary — 'does not itself build, run, profile, modify source, commit, push, tag, or release' — clearly distinguishes this from build/run siblings like build_docker_optimization_candidate.

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 is given about when to use this tool versus siblings such as authorize_docker_session or preview_docker_optimization_session. The phrase 'exact Docker optimization Preview once' implies a preceding preview step, but the description does not state the intended workflow, prerequisites, or when not to use it.

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