Set dry-run mode

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

The description describes the key behavioral trait: write tools return a preview without modifying FL. This adds value beyond the annotations (idempotentHint, openWorldHint) by specifying the effect on write tools. It does not discuss persistence or reset behavior, but is adequate.

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 a single, front-loaded sentence with no extraneous information. Every word contributes to understanding the tool's function.

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 simple boolean toggle tool with an output schema (not detailed), the description provides the essential behavior. It could be improved by briefly noting the output format (the 'planned' preview), but is largely complete given the tool's simplicity.

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 description does not explain the single boolean parameter 'enabled'. While 'When on' hints at the true state, the parameter's role is not explicitly clarified. With 0% schema description coverage, the description should compensate but fails to do so sufficiently.

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 tool sets a dry-run mode where write tools return a 'planned' preview without making changes. It uses a specific verb ('set') and resource ('dry-run mode'), distinguishing it from sibling tools that directly manipulate project elements.

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 when a preview of write actions is desired, but does not explicitly state when to avoid using it (e.g., when actual changes are needed). No alternative tool is mentioned, but the context is clear.

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