Registry Image Sweep

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds valuable behavioral context: 'read-only', enumerating, deduplicating by digest, capping, and scanning. This expands beyond annotations without 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?

A single sentence that is front-loaded with action. Every word earns its place; no fluff. Highly concise and structured.

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 the tool has an output schema and 7 parameters (1 required), the description explains the core workflow (enumerate, dedupe, cap, scan) and safety (read-only). It is complete enough for an agent to understand scope. The max_images default is in schema. No gaps.

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 100%, so baseline is 3. Description does not add meaning specific to parameters (region, profile, etc.) beyond the schema. It explains the overall process but not parameter details, so it stays at baseline.

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 ('sweep') and resource ('entire cloud container registry'), with detailed steps: enumerate, dedupe, cap, scan. It clearly distinguishes from sibling tools like 'registry_lookup' (specific image) and 'scan' (general) by targeting full registry sweeping.

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 clearly implies usage for scanning all images in a registry, but does not explicitly state when not to use or suggest alternatives like 'registry_lookup' for individual images. Good context but lacks exclusions.

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