storage_gateway_add_export

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

No annotations are provided, so the description carries the transparency burden. It does disclose the core creation behavior ('Add a new export'), identifier flexibility, and the returned output. However, it does not mention permissions, idempotency, failure behavior, or what changes when an export is created.

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 compact and well-structured: a one-line purpose, an identifier note, an Args block, and a Returns line. Every sentence adds information; there is no filler or repetition of the schema.

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 tool with a nested export_config and no schema descriptions, this is largely complete: it describes both parameters, their semantics, and the output. It falls short only by not indicating which export_config keys are required or optional.

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%, but the description compensates well by explaining that gateway_identifier accepts a label or ID and by enumerating export_config's keys: label, vfs_uuid, pseudo_root_path, and allowed_ips. This adds substantial meaning beyond the opaque additionalProperties object.

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 says 'Add a new export to a storage gateway,' which is a specific verb plus a specific resource. This clearly separates it from gateway-level sibling operations like storage_gateway_create and from storage_gateway_delete_export.

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 purpose implies when the tool should be used, but the description does not explicitly provide when-to-use guidance, exclusions, or alternative tool names. 'Smart identifier resolution' is helpful input guidance, not usage routing.

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