download_firmware

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

Annotations indicate destructiveHint=true and no readOnly, but the description adds rich behavioral context: asynchronous download, queued task, CPE fetches on next session, large files take minutes, and return value is raw JSON confirmation. This far exceeds what annotations provide.

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 detailed but front-loaded with purpose, then actionable steps, then limitations, and ends with an example. Every sentence is valuable, though it could be slightly tighter without losing information.

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?

Given the absence of an output schema, the description explains the return value (raw JSON confirming task queued) and provides verification guidance. It covers async behavior, file prerequisites, and includes a concrete example. Completely adequate for a 3-parameter tool.

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?

All three parameters are fully described in the input schema (100% coverage). The description adds extra meaning: device_id format and source, file_id verification via genieacs://file/, and default behavior for filename. This adds beyond the schema.

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 specific verb ('push') and resource ('firmware image or configuration file to a CPE device'), and the mechanism ('GenieACS TR-069 download'). It clearly distinguishes from sibling tools like reboot_device or set_parameter.

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 explains when to use the tool (for OTA firmware upgrades or pushing any file) and prerequisites (file must already be uploaded to GenieACS). It also provides context on async behavior and verification. However, it does not explicitly list when NOT to use it, but that is minor given the clarity.

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