list_apps

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

Annotations already provide readOnlyHint=true and openWorldHint=true, which convey the read-only and safe nature of this operation. The description adds context about the scope ('installed apps on the iOS Simulator') and return fields, but does not describe additional behavioral details beyond what annotations already provide.

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 one concise sentence, front-loaded with the action and resource, containing no extraneous information or repetition of the tool name.

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 read-only list operation with one optional parameter and no output schema, the description is adequately complete. It states what is listed and what details are included. Minor gaps like requiring a booted simulator are implied by the 'iOS Simulator' context but not explicitly stated, which is acceptable for such a lightweight 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?

The input schema has 100% coverage for the single optional 'udid' parameter with a clear description. The tool description does not mention the parameter, but the schema fully explains its meaning (target UDID with env var fallback), so no additional semantic value is added by the description.

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 verb 'Lists' and specifies the resource: 'all installed apps on the iOS Simulator'. It also mentions the output fields ('bundle identifiers and display names'), which distinguishes it from sibling tools like install_app or launch_app that perform different actions.

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?

The description implies its use for seeing installed apps, but does not explicitly state when to use it versus alternatives, nor does it mention any exclusion criteria. There is no direct sibling that also lists apps, so the usage context is somewhat implied but not explicitly guided.

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