project_edit_metadata

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

With no annotations provided, the description carries the full burden. It effectively discloses the blocking nature ('waits until the user closes it') and UI modality ('opens a modal dialog'), which are essential behavioral traits for an agent orchestrating tool calls. It could mention undo implications or save behavior, but the core execution pattern is transparent.

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 consists of exactly two sentences with zero waste. The first sentence establishes purpose and capability; the second delivers critical blocking behavior information. Every word earns its place, and the structure front-loads the primary action.

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 simplicity (no parameters, no output schema), the description is appropriately complete. It covers the essential context: what UI element opens, what operations are possible within it, and the critical blocking behavior. It does not need to explain return values as there is no output schema.

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 input schema contains zero parameters. As per the rubric, this warrants a baseline score of 4. The description correctly omits parameter details since there are none to document, focusing instead on the tool's behavioral semantics.

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 uses a specific verb ('Open') with a clear resource ('metadata editor dialog') and scope ('track metadata, title, artist, etc.'). It distinguishes itself from siblings like 'track_set_properties' by explicitly mentioning it opens a 'modal dialog,' signaling interactive UI behavior rather than programmatic property changes.

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?

While it does not explicitly name alternatives like 'track_set_properties,' it provides critical usage context by stating 'the command waits until the user closes it.' This clearly signals that the tool blocks execution and requires user interaction, guiding the agent away from using it in fully automated workflows.

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