bucket_create

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

No annotations are present, so the description must fully disclose side effects. It does so by revealing that object lock force-enables versioning, that the result reflects observed rather than assumed state, and that undo deletes the bucket only while empty. These are non-obvious behavioral traits that go far beyond 'create a bucket.'

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 front-loaded with a one-line summary and then uses short paragraphs for caveats and a labeled Args section. Every sentence provides actionable information, and the structure makes the content easy to scan despite its length.

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?

The tool has four parameters, no annotations, and no output schema, yet the description covers purpose, side effects, reversibility, and all parameter semantics. The caveat about the result reporting observed state is a relevant behavioral detail that helps the agent anticipate response variability. The description is complete for the tool's complexity.

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?

With 0% schema_description_coverage, the description takes on full parameter documentation. It explains all four parameters: bucket_name constraints (3-63 chars, allowed characters), object_lock's permanence, dry_run's preview behavior, and target's default resolution. This adds essential meaning beyond the bare schema titles and defaults.

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 opens with exactly what the tool does: 'Create a bucket, optionally WORM-capable.' This is a specific verb+resource statement that clearly distinguishes it from siblings like bucket_delete, bucket_ls, and set_* configuration tools. The WORM-capable option is a unique differentiator.

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 explicitly states that object_lock=True is 'the ONLY way' to get object lock and that it 'Cannot be changed afterwards,' giving clear when-to-use and when-not-to-use guidance. It also notes that undo deletes the bucket only while empty, warning the user about the reversibility condition. This is strong usage direction beyond simple verb definition.

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