get_workspaces

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

With no annotations present, the description carries the full burden of behavioral disclosure. It does not mention whether the operation is read-only, what data it returns, whether it depends on an open project, or what side effects, if any, it has. 'Get workspaces' only implies retrieval.

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 short but under-specified. The phrase 'Premiere Pro expanded operation' is boilerplate filler, and 'get workspaces' merely restates the tool name. It is concise in length but does not use its sentences to convey meaningful information.

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?

Without an output schema or annotations, the description should explain what the tool returns or how the result should be interpreted. It provides none of this, leaving an agent with only a label and no operational context for a successful 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, so the input schema and description need not document parameter details. The schema is empty and the description adds no parameter information, which is acceptable given the lack of parameters.

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 states a specific verb and resource: 'get workspaces.' This is clear enough to identify the tool as a retrieval operation, but it does not define what 'workspaces' means or distinguish it from related operations like set_workspace beyond the verb.

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 provides no guidance on when to use this tool, what prerequisites exist, or which alternative tools might be more appropriate. It is a bare statement of the operation name with no contextual direction.

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