save_session

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the mutation/safety profile is already structured; the description only adds the implementation detail that it routes through Ardour's save_state. It says nothing about overwrite behavior, whether the session must be open, or what happens on repeated calls, which matters given idempotentHint=false.

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 or repetition. Its brevity is not wasted wording, though the shortness leaves substantive gaps addressed under other dimensions.

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 needn't be described, and annotations cover the safety profile. What is missing is any handling of the opaque request wrapper with its dry_run and expected_revision fields, which is the main thing an agent would need to call this correctly.

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 the single 'request' object, whose nested fields (dry_run, confirm_delete, expected_revision) are never explained. The description is silent on parameters entirely, so it provides no compensation for the coverage gap, and an agent is left guessing why a save operation accepts confirm_delete and expected_revision.

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?

Names a specific verb and resource ('Save current session') and adds the backend mechanism ('through Ardour save_state'), which is more than a restatement of the tool name. It does not, however, distinguish itself from nearby tools such as create_snapshot or get_session_info, so an agent must infer that this persists the live session rather than snapshotting or reading it.

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 explicit when-to-use guidance and no exclusions. In particular, nothing tells the agent whether this differs from create_snapshot, or whether it is safe to call casually or only before risky operations.

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