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

Beyond the annotations, the description discloses the short-lived no-auth download_url, the replay manifest contents, warning examples, and the ACTION-REQUIRED post-unzip place_local_files step. These are concrete behavioral traits an agent needs and are not available from the annotations alone.

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 front-loaded with the core purpose and then covers return shape and required follow-up without obvious filler. It is dense and long, but most detail earns its place because there is no output schema.

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 complex download/build tool with no output schema, the description explains the returned download_url, replay manifest, warnings, and place_local_files follow-up well. The main remaining gap is input semantics, especially the required session_id.

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 coverage is only 50%: the daw parameter has a helpful enum description, but the required session_id has no description in either the schema or the tool description. The description focuses on outputs and post-processing rather than clarifying the inputs.

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 opens with a specific verb and resource: save a session as a native Logic project rebuilt server-side, with no desktop needed. It clearly distinguishes this from desktop-dependent flows, though it does not name the sibling alternative (convert_project) directly in the description; that routing detail appears only in the schema.

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 clear context for when this tool is appropriate: native Logic download, server-side rebuild, no desktop. It does not spell out explicit when-not-use exclusions, but the schema's daw parameter routes non-Logic targets to doseedo_convert_project.

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