create_object_storage

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

Annotations already state readOnly=false, openWorld=true, idempotent=false, and destructive=false. The description adds useful behavioral context beyond annotations: creation is a purchase that may incur cost, only one object storage per location is allowed, and space increases should use the resize endpoint rather than this tool.

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 short and front-loaded with the core action and endpoint. The repeated "Create a new object storage" phrasing is slightly redundant, but the one-per-location note and resize path are relevant and efficiently stated.

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?

For a create/purchase mutation with rich schema descriptions and annotations, the description covers the key agent-facing concerns: what it creates, that it is a purchase, the one-per-location limit, and where to go for resizing. It does not describe the response shape, but the schema and annotations carry enough support that this is a minor gap.

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 the schema already documents all parameters in detail. The description lightly reinforces that region/location and purchased space matter, especially via the one-per-location rule, but it does not add syntax or constraints beyond what the schema provides.

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 gives a specific verb and resource: "Create / purchase a new object storage." It also adds the important constraint that only one object storage can be bought per location, though it does not explicitly name sibling tools such as retrieve_object_storage or upgrade_object_storage for differentiation.

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?

Usage is implied by "Create / purchase a new object storage in your account" and clarified by the one-per-location constraint. It also points to a resize endpoint for increasing space, but it does not explicitly compare this tool with alternatives like upgrade_object_storage or update_object_storage.

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