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

Adds real behavioral context beyond the annotations: 'off' is a sleep state, not a power cut, and the power state is read back after the call because the box can report itself off while still showing a screensaver. This is exactly the kind of latency/state-lag disclosure annotations cannot carry.

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 sentences, front-loaded with the core action, then the semantic clarification, then the readback caveat. Each sentence earns its place, though the final clause is slightly wordy.

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?

With no output schema, the description appropriately explains the readback behavior after the call, giving the agent enough to interpret results. For a two-parameter enum tool, this is nearly complete; only pairing/device prerequisites are unaddressed.

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 100% and already documents both parameters including 'off = sleep'. The description reinforces the 'off' semantics and adds the 'not a power cut' nuance, but does not go materially beyond the schema's own parameter descriptions.

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?

States a specific verb+resource ('Wake an Apple TV or put it to sleep') with unambiguous scope, clearly distinguishing it from siblings like ios_tv_button, ios_tv_status, and ios_tv_swipe.

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 clarifies the meaning of the 'off' state but never states when to prefer this tool over alternatives or any preconditions (e.g. paired device required). Usage is implied rather than guided.

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