ios_set_permission

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

The description adds meaningful behavior beyond annotations: it operates 'without going through the alert' and is limited to the simulator, which are not captured by readOnlyHint or idempotentHint. It does not detail every effect on existing permissions, but the idempotentHint annotation already covers repeat-safety. This is a good balance of added context and annotation reliance.

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, no wasted words. The core function is front-loaded in the first sentence, and the second sentence delivers the critical constraint and alternatives. Every element earns its place.

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 simple mutation tool with a complete input schema and an output schema present, the description covers the essential context: the operation, the platform restriction, and how to handle real devices. There is no missing information an agent needs to select and invoke it correctly.

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%, with each parameter already documented (grant boolean, service allowed values, bundle_id purpose). The tool description adds no additional parameter-specific meaning, so the baseline of 3 is appropriate for a schema that fully carries the parameter semantics.

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 action and resource: 'Set a privacy permission without going through the alert.' This specific verb+resource combination immediately distinguishes it from alert-handling and other iOS control tools. The simulator-only note further narrows scope, making the tool's purpose unambiguous.

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?

Explicit usage guidance is provided: 'Simulator only. On a real phone there is no API for this: drive the Settings app, or answer the permission alert with ios_handle_alert.' This directly tells the agent when to use this tool and which alternatives to choose on real hardware, leaving no ambiguity.

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