list_embedded_buckets

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the return format (a dict with a 'buckets' list), which is helpful, but fails to address critical aspects like authentication requirements, rate limits, pagination, error handling, or what 'embedded' means operationally. This leaves significant gaps for an agent to understand the tool's behavior.

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 the core purpose ('List user embedded buckets.') and efficiently provides a return example. It avoids unnecessary fluff, though the example formatting could be slightly cleaner. Every sentence adds value, making it appropriately concise.

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's low complexity (0 parameters, no annotations, no output schema), the description is moderately complete—it states the purpose and shows a return example. However, it lacks details on behavioral traits (e.g., auth, errors) and doesn't clarify how 'embedded' buckets differ from other bucket types in the sibling tools, leaving room for improvement in contextual understanding.

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 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, so it appropriately focuses on the return value. However, it could have mentioned if any implicit parameters (like user context) are involved, but this is a minor omission given the zero-param baseline.

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 clearly states the action ('List') and resource ('user embedded buckets'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'cloud_storage_list_buckets' or 'list_buckets' (implied from context), leaving some ambiguity about what makes 'embedded' buckets distinct.

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?

No guidance is provided on when to use this tool versus alternatives like 'cloud_storage_list_buckets' or other list tools in the sibling set. The description lacks context about prerequisites, constraints, or typical use cases, offering minimal usage direction.

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