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

No annotations are provided, so the description carries the burden. It discloses the session prerequisite, which is genuinely useful behavioral context. However, it doesn't disclose what an update does to a running session, whether changes are reversible, or what the get response looks like. It adds some value but not rich disclosure for a mutation-capable tool.

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 with no filler. The core purpose and get/update distinction are front-loaded, the prerequisite is stated last. Every sentence earns its place and the structure is easy to scan.

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 2-param tool with a required udid, the description covers both call modes and the session prerequisite. However, with no output schema present, the agent is left guessing what the get operation returns and what settings keys are valid beyond the one example. This is a moderate gap for a settings tool.

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 both parameters (udid, settings) are already documented in the schema, including the example format for settings. The description adds no parameter detail beyond what the schema provides, matching the baseline 3 for full-coverage 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?

States a clear dual-mode verb+resource: 'Get or update iOS automation settings on an iOS device.' The get/update split is explicitly spelled out, and the iOS scope separates it from the broad device/session family. It lacks a named sibling contrast, but no other settings tool exists in the sibling list, so the purpose stands on its own.

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?

Gives explicit invocation guidance for both modes: 'Call without settings to get current values. Pass settings object to update.' It also states the prerequisite 'Requires an active iOS automation session.' It doesn't name alternatives or when-not-to-use cases, but with no obvious sibling for settings this is adequate context.

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