zte_delete_port_forward

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

Annotations already indicate destructiveHint: true and readOnlyHint: false, which inform the agent that this is a destructive operation. The description adds no further behavioral context beyond what annotations provide, such as whether the deletion is irreversible or has side effects.

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 concise, with a single-line summary followed by an Args section. It front-loads the main action. Minor improvements could remove the blank line or simplify the docstring format, but overall it is efficiently structured.

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 it is a simple delete operation with one parameter, the description provides necessary context (source of index) and the tool has both an output schema and annotations covering destructiveness. It does not explain return values, but repetition is mitigated by the output schema. Overall, it is sufficiently complete for its complexity.

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 input schema has one parameter 'index' with type integer but no description (0% schema coverage). The description adds essential context: 'Indice de la regla (obtenido con zte_get_port_forwards)', explaining how to obtain the index. This compensates well for the lack of schema descriptions.

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 'Borra una regla de port forwarding por su indice' (Delete a port forwarding rule by its index). It specifies the verb (delete), resource (port forwarding rule), and method (by index). This distinguishes it from siblings like zte_add_port_forward and zte_modify_port_forward.

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 advises that the index is obtained via zte_get_port_forwards, implying the tool should be used after listing rules. However, it does not explicitly state when to prefer this tool over alternatives (e.g., modify vs delete) or provide any when-not-to-use guidance.

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