appium_mobile_permissions

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

Annotations declare a non-read-only, closed-world tool, and the description correctly reflects that mixed read/write nature plus the platform boundary (iOS reset is Simulator-only, reset is iOS-only). It does not disclose prerequisites such as AppleSimulatorUtils for iOS, permission/entitlement requirements, or what state is lost on reset, so it adds only moderate context beyond annotations.

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?

A single front-loaded sentence pairs the action scope with the platform scope, and the trailing pointer to action-specific parameters is short. The only weakness is that 'See action-specific parameters' spends words without conveying information.

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 an 11-parameter, nested-object tool with no output schema, the description conveys the operation surface but leaves platform prerequisites and the relationship between action and required parameters to the schema. It is adequate given the rich schema, but not self-sufficient for an agent choosing between the three actions.

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 every parameter is already documented in the schema, including action, target, service, access, and permissionChangeAction. The description adds nothing parameter-specific beyond pointing at the schema, which matches the baseline for fully covered schemas.

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 uses specific verbs and a named resource: read/update Android app permissions, read/update iOS Simulator privacy services, and reset iOS privacy prompts. It clearly separates the two platforms, which no sibling tool covers, though it does not explicitly name a sibling it is distinct from.

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?

Platform scoping (Android vs iOS Simulator) implies when each path applies, but there is no explicit when-to-use guidance and no routing away from adjacent tools such as appium_driver_settings or appium_app_lifecycle. 'See action-specific parameters' defers the decision to the schema rather than explaining it.

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