frida_ios_ats_bypass

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

No annotations provided, so description carries full burden. It discloses hooking behavior and allows arbitrary HTTP/self-signed certs, but does not mention reversibility, safety, or side effects like persistent traffic changes.

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?

Three sentences, front-loaded with purpose, then technical details, then parameter. No fluff, every sentence adds value.

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?

Functional but minimal. No output schema, no mention of return values or side effects. Given tool complexity (system security modification), more context on behavior scope and duration would help.

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 has only 'target' with no description (0% coverage). The description adds clear meaning: 'process name or pid (string).' This fully compensates for the schema's lack of parameter documentation.

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 it disables App Transport Security for a target process on iOS/macOS, with specific technical actions (patches NSURLSessionConfiguration, hooks SecTrustEvaluate). It distinguishes from siblings like frida_ios_keychain_dump by focusing on network security bypass.

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 on when to use this tool vs alternatives, no prerequisites or caveats mentioned. The description assumes user knowledge of ATS bypass context without elaboration.

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