nexterm_list_provider_backups

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 the safety profile is fully covered. The description adds only the scoping notion ('stored by one configured provider') and says nothing about pagination, ordering, or what happens when the provider has no backups.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity borders on under-specification given the missing parameter and usage context.

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 is simple, read-only, one parameter, and has no output schema, so the bar is modest. Still, the description leaves the agent without the source of provider_id or any sense of the returned list, which matters because sibling tools like nexterm_list_backup_files could be confused with it.

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% and the single required parameter provider_id carries no description or format hint. The phrase 'one configured provider' weakly signals that provider_id identifies a backup provider, but it doesn't say where to obtain that ID (e.g., from nexterm_get_backup_storage) or what an invalid ID does.

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?

States a specific verb (list) and resource (backups) scoped to one configured provider, which is more precise than a bare 'list backups'. It partially distinguishes itself from siblings like nexterm_list_backup_files and nexterm_delete_backup_provider, but never clarifies how 'backups stored by a provider' differs from the backup files tool.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The only hint is the phrase 'one configured provider,' which implies a single provider_id must be selected, but an agent gets no direction on picking this over nexterm_list_backup_files.

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