download_project

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

No annotations provided, so description carries full burden; it discloses protocol, fallback behavior, and add_loader_anyway parameter, but does not mention potential side effects (e.g., overwriting PLC program, requiring PLC stop state) or return information.

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?

Two concise sentences with no wasted words; every sentence provides essential information about the tool's operation.

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?

Description covers protocol, fallback, and parameter behavior; however, lacks return value info and preconditions like PLC state for a download action, which would enhance completeness.

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 100% with good parameter descriptions; description adds value by explaining fallback behavior for connection and context for add_loader_anyway, exceeding baseline of 3.

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?

Description explicitly states 'Download the compiled CLASS 2 project to a PLC over the Sigmatek online protocol (TCP port 1954)', providing specific verb, resource, and protocol details, and distinguishes from sibling tools like compile_project or deploy_all.

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?

Description mentions fallback to saved connection but lacks explicit guidance on when to use this tool vs alternatives like download_visu_project or deploy_all; no when-not-to-use conditions or prerequisites provided.

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