home

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

With no annotations present, the description carries the full burden, and it does add meaningful behavioral facts: the app session is preserved, the foreground is moved away, and the operation times out after 90 seconds. This goes well beyond a generic 'go home' statement, though it does not cover permissions or failure behavior.

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 short sentences front-load the primary action and then add the two most important qualifiers (session-preserving behavior and 90s timeout). There is no filler or repetition of schema content.

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 one-action device command, the description plus the fully documented 16-parameter schema and existing output schema provide enough to invoke it correctly. It is slightly abstract about platform-specific behavior (tv/desktop home semantics), but that is a minor gap.

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 description coverage is 100%, so the schema already documents all 16 parameters. The description adds no tool-specific parameter meaning, which matches the baseline 3 for full schema coverage.

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 uses a specific verb plus resource ('Send the selected device to its home screen') and adds a differentiating behavioral detail: the app session stays open while the foreground moves away. This distinguishes it from ambiguous navigation siblings like back or app-switcher.

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 phrase 'leaves the app session open but moves the foreground away' implies a use case—backgrounding the current app without closing it. However, it never explicitly names alternatives such as back or app-switcher nor gives a when-not-to-use condition, so guidance remains implied rather than direct.

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