get_project_panel_metadata

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

With no annotations, the description carries the full behavioral disclosure burden. It only restates the operation and adds the unhelpful phrase 'expanded operation'; it does not disclose return shape, side effects, permissions, or what metadata is actually exposed.

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 it is under-specified rather than genuinely concise. 'Premiere Pro expanded operation' is filler that does not earn its place, and the description omits the context needed to make the single sentence useful.

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 and no annotations, so the description must explain what the agent will receive and how this differs from other metadata tools. It does neither, though the zero-parameter signature makes invocation itself straightforward.

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 declares zero parameters, so the baseline is 4 and there is little for the description to add. The schema's additionalProperties: true is unusual, but with no named parameters this does not represent a description failure.

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 names a specific verb and resource: get project panel metadata. However, 'expanded operation' is opaque jargon and the description does not distinguish this from closely related siblings like get_metadata, get_project_item_info, or get_item_info.

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 about when to use this tool instead of alternatives. The sibling list includes set_project_panel_metadata and several generic metadata getters, but the description gives no conditions or exclusions to help an agent choose.

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