raw_set_project

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

With no annotations, the description carries the full disclosure burden. It only says the action 'May open a dialog or change project state' and advises inspecting the command name first; it does not specify side effects, reversibility, permissions, or return behavior. The disclosure is too vague to be actionable.

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 purpose statement. It conveys the core action, the no-argument nature, and a caution about possible side effects in only two sentences, though the vague 'inspect the command name first' advice is somewhat unhelpful.

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?

The tool has no annotations, no output schema, and an empty input schema, so the description is the only behavioral source. It does not explain prerequisites, return values, or what exactly happens when invoked; the advice to inspect the command name shifts responsibility rather than providing complete context.

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 has zero parameters and 100% schema description coverage, so there is no parameter information missing. The baseline for zero-parameter tools is 4, and the description adds no conflicting or unnecessary parameter detail.

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 states a clear, specific action: change project window properties (size, position, caption). It also identifies the tool as a static, no-argument Audacity action, which helps distinguish it from parameter-driven sibling tools like raw_set_clip or raw_set_preference.

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 gives no guidance on when to use this tool versus alternatives. It mentions 'Static no-argument Audacity action' but does not state when this command is appropriate, what prerequisites exist, or when to prefer another project-related tool.

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