scan_buckets_findings

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, indicating a safe read operation. The description adds unique behavioral context: 'Operator-deploy only; degrades to info when unprovisioned' and 'scanId is required so reads can be owner-scoped'. No contradictions 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?

Three sentences, no filler. Front-loaded with main purpose. Every sentence adds value: retrieval action, deployment caveat, and parameter justification.

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?

Output schema exists (not shown) so return values need not be described. Covers prerequisites (completed scan), deployment constraints, and parameter necessity. Could add note about pagination if findings are large, but not critical for basic usage.

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 must compensate. It mentions scanId as required for owner-scoping and notes target/providers are optional filters, but does not explain what these filters filter on (e.g., target name, provider type). Lacks additional context that would help an AI agent correctly populate parameters.

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?

Description clearly states 'Retrieve findings from a completed cloud-bucket discovery scan by scanId.' It identifies the resource (findings), action (retrieve), and prerequisite (completed scan). Distinguishes from siblings like scan_buckets_start and scan_buckets_status through workflow context.

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?

Describes deployment condition ('Operator-deploy only; degrades to info when unprovisioned') and explains scanId requirement for owner-scoping. While it doesn't explicitly list alternatives, the sibling names imply a workflow (start → status → findings), providing sufficient context for an AI agent to use correctly.

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