manage_bundler

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

With no annotations, the description carries the disclosure burden. It adds useful context by noting that platform logs auto-start by default and that PID-based filtering removes system/GMS noise. However, it omits side effects such as what stopping or restarting does to a running session and whether starting blocks or returns immediately.

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 filler: core action first, platform-log default second, and the advanced Android filtering tip last. Every sentence adds distinct value and the most important information is front-loaded.

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 an 8-parameter control tool with no annotations and no output schema, the description is adequate but incomplete. It explains the core lifecycle and one advanced combination, but does not mention expected return behavior, failure modes, or how this tool relates to sibling log tools.

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 high (88%), so the schema already documents the parameters. The description reinforces the key deviceId+packageId combination for Android, but largely repeats what the schema states, putting it at the baseline of 3.

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 opens with a specific verb-resource pair: 'Start, stop, or restart the Metro bundler.' This clearly identifies the tool's function. It does not explicitly differentiate from siblings like manage_platform_logs or get_bundler_logs, so it stops short of a top score.

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?

There is no guidance on when to choose manage_bundler over alternatives such as manage_platform_logs or get_bundler_logs. The only actionable usage advice is parameter-level—the deviceId+packageId combination for Android—rather than tool-selection logic.

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