pipeline_analyze_tool

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

With no annotations, the description carries the full behavioral burden. It hints at a propose/apply split via the params but never says whether proposals are persisted, what audio diagnostics it reads, whether 'apply' mutates the pipeline irreversibly, or if it requires a session/project to be open. For a tool capable of mutation, 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?

A single front-loaded sentence with no filler, and the core action is stated first. It is arguably too terse given the tool's complexity, but there is no wasted text.

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?

An output schema exists, so return values need not be described, but the definition still leaves the tool's lifecycle (propose vs apply), its dependencies, and its 0%-documented parameters unexplained. For a mutation-capable pipeline tool with no annotations, this is incomplete.

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?

Schema description coverage is 0% for both parameters, so the description must compensate and does not. 'apply' (boolean, default false) and 'project_path' (nullable string) are never explained — the reader cannot tell from the description whether 'apply' performs the mutation or merely stages it.

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 gives a specific verb+resource ('propose pipeline param patches') and source ('from audio diagnostics'), which is more than a restated name. However, 'Heuristic Analyze' is jargon, and the definition never differentiates itself from nearby siblings such as pipeline_set_config_tool or audio_diagnostics_tool, so an agent must infer the distinction.

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 statement of when to use this versus pipeline_run, pipeline_set_config_tool, or audio_diagnostics_tool, and no note about prerequisites (e.g. needing a project loaded). The presence of an 'apply' flag implies a propose-then-apply workflow, but the description never explains that flow or when to set it.

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