scan_buckets_start

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

Disclosures async behavior, immediate scanId return, and behavior when unprovisioned. Annotations add no contradiction; description adds value beyond schema and 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?

Two concise sentences with no wasted words. The purpose is front-loaded, and each sentence adds distinct value.

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?

Covers the async flow and links to status and findings tools, but does not explain the output schema (though it exists) and omits parameter details for providers. Adequate but not fully comprehensive.

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 has 0% description coverage. Description only explains 'target domain' for the target parameter; the providers parameter is not explained, leaving a gap. Description partially compensates but is insufficient.

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 explicitly states the tool starts an async cloud-bucket discovery scan for a target domain, distinguishing it from sibling tools by referencing related polling and retrieval tools.

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 clear context: 'Operator-deploy only; degrades to info when unprovisioned.' and directs to poll with scan_buckets_status and retrieve with scan_buckets_findings, but does not explicitly state when not to use or alternatives.

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