lucky_create_port_forward

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

The annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false) already establish this as a non-idempotent write, and the description's 'Create' is consistent with that. Beyond the input-format hint of 'native Lucky JSON object', the description discloses no behavioral traits such as duplicate handling, whether the change takes effect immediately, or what error conditions exist. No contradiction with 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 brief at 13 words in a single sentence, so it is free of fluff. However, the opening clause 'Create a Lucky port forward' largely restates the tool name, leaving only the JSON-object clause as genuinely additive information.

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 a nested free-form JSON parameter, no output schema, and zero schema description coverage, this description is far too thin for an agent to call the tool correctly. It provides no expected return value, no field guidance, and no behavior on conflict or failure, so the agent would be guessing at the input structure.

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% and the sole parameter 'value' is a permissive object (additionalProperties: {}), so the schema conveys almost no meaning. The description's only contribution is the hint that the value should be a 'native Lucky JSON object', but it omits the required fields, nesting, or example shape an agent needs to construct a valid port forward definition.

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 pairs a specific verb ('Create') with a specific resource ('a Lucky port forward'), which clearly signals the operation and distinguishes it from the sibling list/update/delete port forward tools. The qualifier 'using the native Lucky JSON object' adds a hint about the input medium. However, it does not define what a port forward is or what fields it requires, so the purpose is clear but shallow.

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?

No guidance is provided about when to create a port forward versus updating or deleting one, despite the sibling set (lucky_update_port_forward, lucky_delete_port_forward) making such guidance relevant. The CRUD naming implies usage by convention, but the description text itself says nothing about context, prerequisites, or alternatives.

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