iptime_backup_config

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

Annotations already declare non-read-only, non-idempotent, non-destructive behavior. The description adds the useful guarantee that existing files are never overwritten, which aligns with destructiveHint=false. However, it leaves unclear what actually happens if output_path already exists (error vs. unique-name generation) and does not mention authentication or connectivity requirements.

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 sentences with no wasted words. The primary action is front-loaded and the critical safety constraint follows immediately. Every sentence earns its place, and there is no redundancy with the structured 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?

The description covers core action and a key constraint, and the schema/annotations handle parameters and safety profile. But with no output schema, the return value is unspecified, and the 'never overwritten' rule creates ambiguity about collision handling. For a side-effecting download/backup tool, this is a meaningful gap.

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 description coverage is 100%: output_path and router_id are both described with sufficient meaning. The tool description only re-emphasizes that the file should be a new .config file, adding no additional parameter-level detail beyond what the schema already provides, so the baseline score of 3 applies.

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 uses a specific verb ('Download') and identifies both the resource ('current router configuration') and the destination ('a new local .config file'). It does not explicitly contrast with sibling tools like iptime_plan_config_restore or iptime_read, but the action is unambiguous and distinct enough that an agent can infer what it does.

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?

No guidance is provided on when to use this tool versus alternatives such as iptime_read or iptime_plan_config_restore. The 'never overwritten' statement is a safety behavior, not a selection criterion, so an agent gets no help deciding between backup, read, and restore operations.

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