ncloud_serverless_get_backup

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

Annotations already declare readOnlyHint=true, so the description doesn't need to repeat that. However, it adds no additional behavioral context, such as what is returned, error cases, or that it retrieves only automatic (not manual) backups. It's a straightforward get, so the description is adequate but doesn't enrich the annotation profile.

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, compact sentence that includes the REST endpoint for clarity. Every word is purposeful; no filler or redundant phrasing. It is appropriately sized for a simple get operation.

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 low complexity (two well-documented parameters) and the readOnlyHint annotation, the description is sufficient for an agent to understand the basic operation. It does not describe the return format, but for a simple get without an output schema, this is a minor omission. The tool is complete enough for correct invocation.

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 both parameters (clusterName and backupName) have detailed descriptions including constraints. The tool description adds no extra meaning about parameters, so it meets the baseline for full schema coverage without needing to compensate.

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 clearly states the action ('Get one automatic backup') and the specific resource (backup within a cluster). It distinguishes this from listing backups by specifying 'one', and the REST endpoint provides precise identification. The verb+resource is unambiguous and matches the tool name.

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 provides no guidance on when to use this tool versus alternatives like ncloud_serverless_list_backups or ncloud_serverless_get_imported_backup. It does not mention prerequisites (e.g., calling list_backups first) or exclusions. The only hint is the endpoint itself, which is insufficient for an agent to decide between this and other backup-related tools.

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