compare_container_measurements

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

Annotations already indicate idempotentHint=true and destructiveHint=false, but the description adds no information about side effects, authorization requirements, failure modes, or what the comparison actually produces. The evidence-type list is semantic context, not behavioral disclosure. There is no contradiction with annotations.

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 front-loaded sentence with no filler. It communicates the core operation immediately, though the long list of evidence types makes it dense and somewhat jargon-heavy.

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?

An output schema exists, so return-value documentation is partly covered. However, with six required ID parameters and zero property descriptions, the description does not explain how to obtain or select those IDs, what 'bound profile' or 'treatment' evidence means, or how the optional thresholds affect behavior. This is insufficient for reliable invocation.

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%, and the description does not explain any of the eight parameters. The evidence categories mentioned (profile, benchmark, correctness, treatment, resource) only vaguely map to the required measurement, analysis, and benchmark IDs, and the optional threshold parameters minimum_delta_percent and minimum_practical_impact_percent are left entirely unexplained.

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 action and resource: 'Compare two Docker measurements' and enumerates the evidence dimensions involved (bound profile, absolute benchmark, correctness, treatment, whole-container resource). This is clearer than a tautology and helps distinguish it from profile-only or benchmark-only siblings, but it does not explicitly differentiate it from the similarly named compare_docker_optimization_iterations.

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?

There is no guidance on when to use this tool versus alternatives such as compare_profiles, compare_benchmarks, or compare_docker_optimization_iterations. The phrasing implies it is for comparing container measurement evidence, but no explicit when-to-use or when-not-to-use boundaries are provided.

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