connect

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

No annotations exist, so description carries all behavioral disclosure burden. It mentions prerequisite and spawn behavior but lacks details on side effects, authentication, session creation, or error scenarios.

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 wasted words. The main purpose and key usage are front-loaded, making it efficient.

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 no output schema, the description does not explain return values or state after connecting. It is adequate for a simple connection tool but missing some contextual completeness.

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 coverage is 100%, baseline is 3. Description adds nuance for spawn parameter ('reliable adb-based launch') but doesn't significantly enhance other parameters 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?

The description clearly states the tool connects to an app by bundle ID, name, or PID. It also distinguishes itself from sibling tools by noting it must be called before others and that spawn=True uses adb-based launch instead of Frida spawn.

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?

Explicitly says 'Must call before using other tools', providing clear when-to-use context. The spawn option is noted but no explicit exclusions or alternative tool comparisons beyond that.

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