analyze_plot_spectrum

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

With no annotations provided, the description carries the full burden. It states that the tool opens a Plot Spectrum window and targets the selected audio, but it does not explain what the window shows, whether it returns any data, or what happens if no region is selected. It is minimally transparent but not rich.

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?

Two short sentences: the first states the action and target, the second states the required precondition. Every sentence earns its place and the content is front-loaded.

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 parameterless UI action tool with no output schema and no annotations, the description covers the essential details: what it opens, what it operates on, and the needed pre-selection. It is slightly incomplete in not explaining the nature of the Plot Spectrum window, but it is sufficient 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?

There are zero parameters and no output schema, so the schema itself provides no semantics beyond an empty object. The description adds meaningful context by indicating the tool acts on 'selected audio' and requires a region, which is more useful than the empty schema alone.

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') and a specific resource ('Plot Spectrum window') on the selected audio, so its purpose is clear. It does not explicitly distinguish itself from sibling analysis tools like analyze_contrast, but the named window is distinctive enough to avoid major confusion.

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 a clear prerequisite: 'Select a region first.' This tells the agent the state required before invoking the tool. It lacks explicit when-not-to-use guidance or named alternatives, but for a zero-parameter UI action this is adequate context.

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