get_bin_contents

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

With no annotations, the description carries full responsibility for behavioral disclosure, but it only implies a read operation through the verb 'get'. It does not state whether there are side effects, whether it depends on a selected bin, or what the output structure is. This is a significant gap.

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 one short sentence, but it is under-specified rather than usefully concise. It repeats the tool name and adds no information that helps invocation. The brevity is not accompanied by substance.

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?

There is no output schema, no annotations, and no parameterized input, so the description must explain the operation's context and return value. It does neither: the agent is never told which bin is inspected, what 'contents' means, or what shape the result takes. This is inadequate for correct invocation.

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 and the schema is essentially empty, so the description has little parameter semantics to add. Per the baseline for 0-parameter tools, this is acceptable. The additionalProperties: true is unexplained, but this is unlikely to be a decisive gap for an agent.

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 'get bin contents' is essentially a restatement of the tool name, offering no additional specificity such as which bin is targeted or what kinds of contents are returned. The prefixed 'Premiere Pro expanded operation' does not distinguish this tool from the many other Premiere-related siblings. This borders on tautology.

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 related tools like get_insertion_bin, get_project_item_info, or list_project_items. The description provides no context about which workflow or state it applies to, so an agent receives no help in selection among siblings.

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