desktop_is_locked

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

The description repeats the readOnlyHint annotation by stating 'Read-only,' but adds minimal extra context ('over BLE'). No additional behavioral traits like side effects, permissions, or rate limits are disclosed. Since annotations already cover safety, the description adds little value beyond redundancy.

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 sentence, front-loaded with the core question, and contains no unnecessary words. It is highly concise and efficient.

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?

For a simple boolean check tool with no parameters and an output schema, the description is adequate but lacks context about return values or usage scenarios. It does not mention that the output is a boolean or any edge cases, leaving gaps that the output schema likely fills but the description could supplement.

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?

There are zero parameters, and schema coverage is 100%. The description correctly does not add parameter details since none exist. Baseline 4 is appropriate for no-parameter tools.

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 the tool checks if the Flipper's desktop is PIN-locked, using a question format. It includes a 'Read-only' tag aligning with annotations. However, it does not explicitly differentiate from sibling tools like app_lock_status, limiting clarity for selection.

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 on when to use this tool versus alternatives. Sibling tools like app_lock_status and desktop_unlock exist, but the description offers no context for choosing this over them, making it hard for an agent to decide when to invoke it.

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