Create a bin

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

Annotations only declare destructiveHint=false, so the description adds genuinely new behavioral context: the authorization requirement (Editor role) and the fact that it returns the new bin including its id. It does not cover idempotency, label uniqueness, or nesting side effects for parentId, but the added auth and return details exceed the annotation baseline.

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?

Three short sentences, front-loaded with the action and result, then the permission constraint. Every sentence carries information an agent needs; no filler.

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 two-parameter mutation with no output schema, the description correctly compensates by stating the return payload (new bin with id) and the auth requirement. The only omitted items are failure modes (duplicate label, invalid parentId), which would make it fully self-sufficient.

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 100%, so both 'label' and 'parentId' are already documented with examples and purpose. The description adds no extra parameter semantics beyond the schema, which is the expected baseline rather than a gap.

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?

Specific verb+resource: 'Create a new bin to collect videos in' immediately tells the agent what it produces and what a bin is for. It is distinguishable from siblings like list_bins and add_video_to_bin, though it never names a sibling explicitly.

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 supplies a real prerequisite ('Needs an API key with the Editor role'), which tells the agent when the call can succeed. However, it gives no guidance on when to create a bin versus reusing one, nor any reference to alternative tools such as list_bins for checking existing bins.

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