GET /settings/backups/download/{file}

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds nothing beyond that boilerplate — critically, it never says the response is a binary file payload rather than JSON, which is the one behavioral fact an agent most needs here.

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?

It is short, but the second sentence ('Generated from Snipe-IT OpenAPI operation backupsdownloadfile') is pure generator noise that repeats the first sentence's route with no added information. Nothing is front-loaded beyond the path itself.

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 file-download endpoint with no output schema, the description should explain that the call streams back a backup archive and note the permission requirement; both are absent. An agent has to guess at return type and authorization from the URL alone.

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% and the single 'file' parameter is documented as 'The short name of the file to download'; the description adds no further semantics such as acceptable filename format or where the name comes from. With full schema coverage, baseline 3 is the correct ceiling for a description that contributes nothing extra.

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 is a restatement of the route path and the operationId ('backupsdownloadfile'), so the resource (backups) and verb (download) are only inferable from the URL tokens, not articulated. It never says in plain language that it retrieves a generated Snipe-IT backup file, and it draws no distinction from configuration/backup siblings such as snipeit_gen_backups_1.

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 statement of when to use this endpoint, no prerequisite (e.g. admin permission needed to download backups), and no pointer to any alternative sibling tool. Nothing tells an agent whether this is the right call versus snipeit_gen_backups_1 or snipeit_raw_request.

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