next_app

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

With no annotations, the description must disclose behaviors. It mentions an optional clock_index but fails to describe what happens if no next app exists, whether it loops, or any side effects. This is insufficient for a loop action.

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: one for purpose, one for the parameter. Front-loaded and no wasted words.

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?

The tool is simple, but the description omits behavioral details like looping behavior or error handling. An output schema exists but the description does not reference it. Still, it covers the essential action and parameter.

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?

Despite 0% schema coverage, the description explains the parameter clock_index as an optional 0-based index defaulting to the first clock. This adds meaning beyond the schema, which only defines type as null or integer.

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 'Switch to the next app in the display loop,' which is a specific verb and resource. It distinguishes from siblings like previous_app or switch_to_app by focusing on moving to the next in a loop.

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 implies usage for cycling forward through apps but provides no explicit guidance on when to use or not use this tool versus alternatives like previous_app or switch_to_app. No exclusions or context are given.

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