dump_current_activity

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

The description states 'dump' implying a read operation, but it does not specify the output format, whether it includes full package name or just activity, or any potential side effects. With no annotations provided, the description carries the full burden and falls short.

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?

The description is a single sentence that is concise and front-loaded. It contains no unnecessary information and 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 tool with zero parameters and no output schema, the description is mostly sufficient but lacks detail on the return value format. It is acceptable given the simplicity but could mention the exact output structure.

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?

There are no parameters, so the schema already covers everything. The description does not add any parameter-level meaning, but since there are none, a baseline of 4 is appropriate.

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 that the tool dumps the current activity name of the connected Android device. The verb 'dump' and resource 'current activity name' are specific, and it is distinct from sibling tools like dump_ui_hierarchy which provide more comprehensive UI information.

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?

No guidance is given on when to use this tool over siblings. For instance, it does not explain when to use dump_current_activity versus dump_ui_hierarchy or other tools. The context signals indicate no additional guidance is provided.

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