input_home

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

The description mentions it 'simulates' an event, but does not disclose that this may be restricted to Android devices or whether it affects the app under test. It also doesn't note potential side effects like minimizing the current app.

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 waste, and the key action is front-loaded. Efficient and to the point.

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 tool, the description is mostly complete. However, it lacks details on the device platform (e.g., only Android) and the expected device state (e.g., device unlocked), which are useful for an agent to call it correctly in a broader 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?

The tool has zero parameters, so the schema is complete and the description correctly states 'No parameters are required.' The description adds minimal but sufficient context beyond the schema.

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 ('simulates') and resource ('home button event') with clear scope ('on the connected Android device'). Distinguishes from siblings like input_back and input_keyevent by naming the exact button.

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?

Provides no guidance on when to use this tool versus alternatives. For example, it doesn't note that it only works on Android or that it should be used to exit to the home screen, nor does it mention alternatives like input_keyevent for system keys.

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