verify_ledger_firmware

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds substantial behavioral context: 'One USB round-trip; never throws — surfaces every failure as a structured verdict', the exact APDU command, and the mode requirement. This goes well beyond the 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 fairly long but efficiently packed. It front-loads the key purpose and then provides necessary details in a logical order. Every sentence adds value, though some internal details (like the full APDU command) could be considered extraneous for usage decisions, but they still enhance transparency.

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?

There is no output schema, so the description must explain return values, which it does exhaustively (seven structured verdicts). It also covers prerequisites, mode requirements, and error conditions. For a tool with no parameters and no output schema, this is exceptionally complete.

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 no parameters, so schema coverage is trivially 100%. The description adds meaning by explaining what data is checked and the possible return values, but since there are no parameters to document, the baseline is 4.

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 a specific verb+resource: 'READ-ONLY firmware-pinning check' that reads firmware version and asserts against a manifest. It distinguishes itself from siblings like get_ledger_device_info or verify_ledger_attestation by detailing its exact purpose and structured outputs.

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 explicitly states a critical prerequisite: 'REQUIRES the device to be in DASHBOARD MODE — no app open. Ask the user to close every Ledger app...' It also explains that opening an app will result in a 'wrong-mode' verdict. However, it does not explicitly name alternative tools or conditions when not to use this tool, which would have earned a 5.

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