Apagar/bloquear pantalla

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

Beyond the annotations, it explains the immediate screen-off behavior, the conditional macOS lock when password is required (defaulting to yes), and that the machine stays powered on. This gives a clear behavioral model without needing to infer from readOnlyHint=false.

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?

Three short, purposeful sentences that front-load the primary action and then add the two most important behavioral caveats. No filler or repetition.

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 zero-parameter, no-output-schema tool, the description covers the action, the locking condition, the default behavior, and the machine state. It is complete enough for an agent to invoke the tool safely and predict the outcome.

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 tool has zero parameters, so the description cannot add parameter detail; the baseline of 4 applies. There is no missing schema information to compensate for.

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 opens with a concrete verb+resource: 'Apaga la pantalla de inmediato' (turns off the screen immediately), and clarifies that the Mac remains on, differentiating it from power-off tools. This is specific enough for an agent to know what action it performs.

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 states the effect but does not explicitly explain when to choose this tool over siblings like sleep, shutdown, or restart. The context implies it is for turning off the display while keeping the Mac running, but it never names alternatives or sets exclusion conditions.

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