Get VM package

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile needs no restating. The description adds modest context about what the response includes (CPU/memory/disk limits), but says nothing about behavior when the UUID is unknown or invalid.

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?

One tight sentence that front-loads the action, the cardinality ('one'), the key, and the returned fields. There is no redundant or filler wording to remove.

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 single-parameter read tool with full schema coverage and rich annotations and no output schema, this is nearly sufficient. The only gap is disambiguation from get_vm_package_by_label and any note on missing-package behavior.

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 id field already explains it is a UUID sourced from list_vm_packages. The description's 'by its UUID' merely echoes the schema, adding no format or validation detail beyond it, so the baseline 3 applies.

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 and resource (get one VM package) with the lookup key (UUID) and the notable payload (CPU/memory/disk limits). It implicitly separates itself from the sibling list_vm_packages, but not from get_vm_package_by_label, which is the other single-package getter.

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 phrase 'by its UUID' implies the precondition that you must already hold an identifier, and the schema points at list_vm_packages as the source. However, there is no explicit when-to-use statement and no routing to get_vm_package_by_label for label-based lookup, leaving the agent to infer the alternative.

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