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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered by structured data. The description adds one genuinely useful behavioral fact not in the annotations ('No automation session required'), but says nothing about whether app data/containers are removed, error behavior when the app is absent, or whether the device must be unlocked.

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 short sentences, zero filler, with the action and target front-loaded and the operational caveat placed second. Nothing here needs trimming.

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 two-parameter, no-output-schema tool whose annotations carry the destructive/idempotent profile, the description covers what the agent needs to call it correctly, including the session-free calling condition. It stops short of explaining post-uninstall state or failure modes, but those gaps are minor at this complexity.

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% with only two parameters, both documented in the schema, so the baseline is 3. The description's 'by bundle ID' merely restates the bundleId schema description and adds no format or syntax detail (e.g., reverse-DNS form, case sensitivity).

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?

States a specific verb and resource ('Uninstall an app from an iOS device') and narrows the target to a bundle ID, which is enough to separate it from generic device tools. It does not, however, explicitly differentiate from close siblings like ios_kill_app, ios_terminate_app, or device_uninstall_app, so the agent must infer the distinction.

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 automation session required' is real usage context: it tells the agent this can be called without an active session, which matters in a toolset where most ios_* tools need one. Beyond that there is no guidance on when to prefer this over ios_kill_app/ios_terminate_app or what prerequisites (device connected, app installed) apply.

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