Send Remote Key

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

The description states it sends a remote key, which is a write/mutation action, but annotations declare readOnlyHint=true and idempotentHint=true, which contradicts the described behavior. The description does not correct or address this discrepancy.

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?

Two sentences with no redundant information. The first sentence clearly states the action, and the second provides a helpful analogy. Every word earns its place.

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 tool with two parameters, no output schema, and exhaustive schema coverage, the description is complete. It explains what the tool does, gives examples, and provides an analogy for context.

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%, so baseline is 3. The description provides examples for the 'key' parameter and references another tool for the full list, but this adds minimal value beyond the schema. For the 'device' parameter, the description repeats the schema's description exactly.

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 verb 'Send' and the resource 'ECP remote key' to a Roku device, with concrete examples like 'Home', 'Up', 'Select', 'Play'. It also distinguishes itself from siblings (e.g., input_text, deep_link) by specifically targeting remote key presses.

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 says it 'mirrors what the user does with the on-screen remote,' which implies its use case but does not explicitly state when to use it versus alternatives like input_text or deep_link. No exclusions or when-not conditions are provided.

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