frida_ios_device_prepare

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

No annotations are present, so the description must fully disclose behavior. It only says 'summarize readiness,' which is minimal. It does not indicate whether it checks connection, installs anything, verifies permissions, or what side effects it has.

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 a single sentence, which is concise but overly terse. It could include more useful information without being verbose, such as parameter roles or output expectation.

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 complexity of device preparation and the lack of output schema, the description is insufficient. It does not explain what readiness means, what the tool returns, or how the parameters affect behavior.

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 0%, and the description does not explain the two parameters (bundle_id, device_id). The agent cannot infer their purpose or how to use them correctly.

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 it summarizes iOS/macOS USB-device readiness for Frida analysis, which indicates a checking/reporting function. However, it is vague about what 'readiness' entails, and while it distinguishes from Android sibling tools (frida_android_device_prepare), it doesn't specify the exact scope or output.

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 (e.g., frida_android_device_prepare or other Frida setup tools). There is no mention of prerequisites, when not to use, or typical workflow context.

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