inspect_docker_optimization_capability

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral specificity by stating it 'never builds, pulls, runs, profiles, or modifies source' and clarifying the scope is 'fixed local,' which aligns with openWorldHint=false. No contradiction.

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 sentences, front-loaded with the inspection scope and followed by a concise side-effect guarantee. Every sentence adds value and there is no filler.

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?

For a no-parameter, read-only inspection tool, this description is complete: it enumerates what is inspected, states that it is non-mutating, and the output schema covers return structure. The only minor gap is explicit sibling differentiation, which is not critical given the clear scope.

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 tool has zero parameters and schema coverage is 100%, so the description has little parameter burden. It appropriately focuses on what the inspection covers rather than argument syntax.

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?

States a clear inspection verb with a specific, enumerated resource scope: fixed local Docker/Buildx/Builder identities, project build contract, Benchmark requirement, base-image presence, and Collector modes. This distinguishes it from sibling inspection tools like inspect_docker_capability and inspect_collection_capabilities.

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 a read-only pre-flight inspection role but does not explicitly state when to use this tool over alternatives such as inspect_docker_capability or preview_docker_optimization_session. No exclusions or sibling comparisons are provided.

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