flipper_gpio_write

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

Annotations indicate readOnlyHint=false and destructiveHint=false, consistent with a write operation. The description adds the behavioral detail that the pin must be configured as OUTPUT, which is useful. However, it does not elaborate on side effects or error handling. With annotations covering safety, this is adequate but not rich.

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?

Single sentence, 13 words, front-loaded with the verb and condition. No redundancy or unnecessary detail. Every word earns its place.

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?

Tool has 3 parameters and no output schema. Description covers the main action but omits error conditions (e.g., what happens if the pin is not set as output) and return values. For a simple GPIO write, this may be minimally sufficient, but missing context limits agent confidence.

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 coverage is only 33% (only 'port' has a description). The description does not add semantic meaning for 'pin' or 'value' beyond the schema's enums. For example, it does not explain what logic levels 0 and 1 correspond to (e.g., low/high voltage). With low coverage, the description should compensate but fails to.

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?

Description clearly states the action: 'Set the logic level of a GPIO pin configured as OUTPUT.' The verb 'set' and resource 'GPIO pin' are specific, and the condition 'configured as OUTPUT' distinguishes it from sibling tools like flipper_gpio_read (read) and flipper_gpio_set_mode (set mode).

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 explicit guidance on when to use this tool over siblings. The description implies the pin must be an output, but does not mention when to choose write vs read or set_mode. No exclusions or alternatives provided.

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