get_top_activity

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

No annotations are provided, so the description carries the full burden. It mentions the return type ('str: Top activity information as JSON'), which adds some behavioral context about output format. However, it doesn't disclose critical traits like whether this is a read-only operation, if it requires permissions, latency, or error conditions. For a tool with zero annotation coverage, this is insufficient.

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 brief and front-loaded, with two sentences that directly state the purpose and return value. There's no wasted text or redundancy. However, it could be slightly more informative without losing conciseness, such as by clarifying 'top activity' in the first sentence.

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?

Given the tool has 0 parameters, 100% schema coverage, and an output schema exists (implied by 'Returns: str'), the description is minimally adequate. It covers the basic action and output format but lacks context on behavior, usage, or integration with sibling tools. For a simple query tool, this is passable but leaves gaps in understanding its role.

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 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, as there are none to explain. This meets the baseline for a parameterless tool, with no gaps to compensate for.

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 states the tool 'Get information about the current top activity', which provides a basic verb+resource combination. However, it's vague about what 'top activity' means (e.g., foreground app, system status, user activity) and doesn't distinguish it from sibling tools like 'get_screen_info' or 'get_packages', which might overlap in functionality. The purpose is understandable but lacks specificity.

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 provided on when to use this tool versus alternatives. With many sibling tools related to device state (e.g., 'get_screen_info', 'get_packages'), the description doesn't clarify if this is for app-focused queries, system monitoring, or other contexts. There's no mention of prerequisites, timing, or exclusions, leaving usage ambiguous.

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