Verify Database S3 Access

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

Goes well beyond the annotations: it discloses the exact assume-role flow, the write/read/delete probe object behavior, that both buckets must share the cluster region, the destructive-in-practice temporary write, the externalId trust-policy matching requirement, org-admin auth, and retry safety with IAM propagation delay. This is consistent with idempotentHint=true, destructiveHint=false, and readOnlyHint=false.

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?

Bold-labeled sections (Purpose, Returns, Behavior, Safety, Auth, Reliability) front-load the essential facts, and every sentence carries decision-relevant content without padding.

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?

Despite no output schema, the description states the return shape ('whether access was verified and a human-readable result message') and covers behavior, safety, auth, and retry semantics for a 4-parameter nested-object tool. Nothing an agent needs to call it correctly is missing.

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 already 100%, so the baseline is 3, but the description adds real meaning: paths are optional and default to the bucket root, both configured buckets must be in the cluster environment's AWS region, and externalId must exactly match the IAM trust policy value.

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 specific verb and resource ('Verify that RawTree can use a customer IAM role to access customer-owned S3 storage') and scopes it temporally ('before creating a database'), which separates it from the sibling verify-cluster-s3-access.

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?

Clearly frames the context ('before creating a database') and lists the exact inputs to confirm first, giving strong usage guidance. It never explicitly names verify-cluster-s3-access or states when *not* to use this tool, so it stops short of full routing guidance.

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