pve_get_node_subscription

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

No annotations are provided, so the description carries full burden. It states this is a 'Get' operation (implying read-only), but doesn't disclose any behavioral traits like authentication requirements, rate limits, error conditions, or what format the subscription status returns. For a tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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 extremely concise at just three words: 'Get node subscription status'. It's front-loaded with the core action and resource. There's zero wasted language or unnecessary elaboration, making it efficient for quick comprehension.

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 tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'subscription status' means in this context (Proxmox VE subscription?), what values might be returned, or any behavioral considerations. The agent would need to guess about the tool's behavior and output format based solely on the minimal description.

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?

The description adds no parameter information beyond what's in the schema (100% coverage). The schema already documents the single 'node' parameter with description 'Node name'. Since schema coverage is high, the baseline score of 3 is appropriate - the description doesn't add value but doesn't need to compensate for schema gaps either.

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 'Get node subscription status' clearly states the verb ('Get') and resource ('node subscription status'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'pve_get_node_status' or 'pve_get_node_version' that also retrieve node information, leaving ambiguity about when to use this specific tool versus other 'get' operations.

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. With many sibling tools starting with 'pve_get_node_' (e.g., pve_get_node_status, pve_get_node_version), there's no indication whether subscription status is a subset of general node information or a distinct query. No prerequisites, exclusions, or comparison to other tools are mentioned.

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