raw_manual

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

With no annotations, the description carries the behavioral burden. It discloses that the tool 'may open a dialog or change project state,' which is valuable caution beyond the simple 'open in browser' statement. The warning is somewhat vague but still meaningfully 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 is short and front-loaded with the main action in the first sentence. The 'Manual:' prefix is slightly redundant with the tool name, but every other phrase adds useful context.

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 zero-argument tool with no output schema, the description gives enough to understand how to invoke it: open the manual with no arguments. The side-effect warning is vague but does not prevent 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?

The input schema is empty, so parameter semantics are fully covered by schema structure; 0-parameter tools receive a baseline of 4. The description reinforces that this is a 'no-argument' action but does not need to add parameter details.

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 clearly states the action ('Open Audacity's manual in the default web browser') and the subject resource, so an agent can understand what the tool does. It is specific enough to be distinguishable from unrelated raw_* commands, though it does not explicitly differentiate from similar help/about siblings.

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 implies usage by calling it a 'Static no-argument Audacity action' and warns to 'inspect the command name first.' However, it does not explicitly state when to prefer raw_manual over alternatives like raw_help or raw_quick_help, nor does it give clear exclusions.

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