backup_queue

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

With no annotations provided, the description carries the full burden of explaining behavior. It transparently discloses that a timestamped file is created and that the operation is a backup, which implies the original is not modified. However, it does not state what happens when dest_dir is null, whether directories are created, or what the command returns.

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 unnecessary words. It efficiently communicates the action, the resource, and the output format.

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 tool has no output schema and no annotations, so the description must be contextually sufficient on its own. It leaves important gaps: the default behavior of dest_dir is unstated, there is no indication of how to identify a valid profile, and the result or return value is not described. These are material gaps for an agent selecting and invoking the 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?

Schema description coverage is 0%, so the description must compensate. It clarifies that 'profile' refers to a queue profile and that the backup target is a timestamped file, but it does not explain the semantics of the optional 'dest_dir' parameter, including what a null value means or where the backup goes by default.

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 ('back up'), a specific resource ('a queue profile's feeds.json'), and a concrete outcome ('to a timestamped file'). This clearly distinguishes it from the listed siblings, which cover listing, searching, and queue mutation rather than backup.

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?

There is no guidance on when to use this tool versus alternatives, no mention of prerequisites like first listing profiles, and no warning about destructive or non-destructive usage. The description simply defines the action without situating it in a workflow.

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