get_vps_backup_cost

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

The readOnlyHint and idempotentHint annotations already cover the safety profile, so the description does not need to over-explain side effects. It adds useful workflow context by noting this should be called before creating a backup, but it does not disclose response details or edge cases.

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 only one short sentence with no filler. It front-loads the action and includes the key timing note about create_vps_backup.

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 simple one-parameter read-only operation with annotations covering safety, the description is largely complete. It clearly states purpose and timing, though it omits return format or units, which would be helpful but not essential for this 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 coverage is 0%, so the description carries the burden of explaining vps_id. The phrase 'of this VPS' only weakly maps to the parameter, and no additional detail is given about the ID format, required ownership, or how the cost is calculated.

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 identifies the operation as retrieving the cost of a new backup for a specific VPS. The phrase 'before calling create_vps_backup' distinguishes it from listing existing backups or querying general VPS pricing.

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?

It explicitly frames the tool as a pre-step to create_vps_backup, giving the agent clear timing context. It does not explicitly discuss when not to use it or list alternatives, but there is no closely competing sibling for this specific task.

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