power_off

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is known. The description adds a useful behavioral nuance by specifying standby rather than a hard power cut, but provides no further side-effect detail.

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 short phrase that conveys the action, target, and resulting state with no filler. It is appropriately sized for a parameterless command.

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 parameterless command with annotations covering mutability, idempotence, and destructiveness, the description provides enough context to invoke the tool correctly. No output schema is present, but none is essential for a fire-and-forget power command.

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 and the input schema already covers this fully (100% coverage). The baseline of 4 applies because there are no parameter semantics for the description to clarify.

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 names a specific action ('Eteint' = turns off), the exact resource (the Philips TV), and the resulting state (standby). This clearly distinguishes it from siblings like power_on and screen_off.

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 intended use is implied by the action ('turn off the TV'), but no explicit guidance is given about when to prefer this over screen_off or power_on. There are no prerequisites to document since it takes no parameters.

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