Intercept Android App via Frida

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it 'Automatically disables most certificate pinning' (a security bypass feature), requires a rooted device and Frida server (permissions/environment), and references setup tools (prerequisites). It doesn't mention rate limits, error handling, or what 'intercept' entails operationally, but covers critical context.

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 front-loaded with the core purpose, followed by key behavioral detail and prerequisites. All three sentences earn their place: first states what it does, second adds a critical feature (certificate pinning disable), third specifies requirements and setup steps. Zero 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?

For a complex tool with no annotations and no output schema, the description does well: it explains the purpose, key behavior, and prerequisites. It could be more complete by detailing what 'intercept' means (e.g., traffic capture, code injection) or output expectations, but given the sibling tools (like 'capture_traffic'), context is partially covered. The high schema coverage helps.

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 100%, so the schema fully documents all parameters. The description adds no parameter-specific information beyond what's in the schema. However, it implicitly contextualizes parameters by mentioning the interception process and setup tools, but doesn't explain individual param roles. Baseline 3 is appropriate given high schema coverage.

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 specific action ('Intercept a specific Android app using Frida dynamic instrumentation') and distinguishes it from siblings like 'frida_ios_intercept' (different platform) and 'intercept_android_adb' (different method). It specifies the technology (Frida) and target (Android app).

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 explicitly states prerequisites ('Requires a rooted device with Frida server running') and directs to specific sibling tools for setup ('use frida_android_setup and frida_android_launch first'). It also implies when to use this tool vs. alternatives by specifying the Frida-based Android interception method.

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