list_firewall_rules

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description is not required to repeat those. It adds a slight nuance with 'currently applied' but this is essentially inherent to 'list'. No additional behavioral context (e.g., no pagination, no rate limits) is disclosed, but the safety profile is already covered by annotations.

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, concise sentence that is front-loaded with the key information. Every word earns its place, and there is no redundancy or fluff.

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?

This is a simple read-only operation with one required parameter and no output schema. The description is sufficient for an agent to understand what to call, though it does not specify the return format (e.g., an array of rule objects). Given the simplicity and annotation coverage, the description is almost complete but leaves a minor gap about the response shape.

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% – the schema only provides the parameter name 'vps_id' with type string. The description says 'this VPS', which implicitly references the parameter but does not explain its meaning, format, or constraints beyond what the name conveys. Given the low coverage, the description should compensate but does not add meaningful detail.

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 states a specific action ('List'), a resource ('firewall rules'), and a scope ('currently applied to this VPS'). It clearly distinguishes from siblings like update_firewall_rules (which modifies) and list_vps (which lists VPSs). The verb and resource are unambiguous.

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 guidance on when to use this tool versus alternatives, no mention of prerequisites, and no exclusions. It does not reference update_firewall_rules or explain that this is the read-only counterpart to modifications. An agent must infer usage context from the name and siblings.

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