list_embedded_buckets

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

The description includes a return type and example response structure (Dict with 'data' containing 'buckets' list), which adds some transparency. However, since there are no annotations, the description carries the full burden and does not disclose authentication requirements, potential errors, pagination behavior, or side effects.

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 very brief and front-loaded. The return example is useful and appropriately compact, with no wasted words.

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?

Given the tool has no parameters and no output schema, the description provides the essential return structure. However, it does not explain what 'embedded buckets' are or how this differs from similar tools like cloud_storage_list_buckets, which could lead to selection confusion. The simplicity of the tool mitigates this 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?

The tool has zero parameters, so the schema already captures the absence of inputs. The description does not need to elaborate, and the baseline for zero-parameter tools is 4.

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 explicitly states 'List user embedded buckets,' which identifies the action and resource clearly. The qualifier 'user embedded' helps distinguish it from the sibling tool cloud_storage_list_buckets, which likely lists cloud storage buckets instead.

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?

There is no guidance on when to use this tool versus alternatives like cloud_storage_list_buckets or other listing tools. No context is provided about use cases, prerequisites, or selection criteria.

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