System Read Preference Domain

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

The description discloses no behavior beyond the tool name. Annotations provide only openWorldHint, idempotentHint, and destructiveHint, none of which are explained; there is no note about read-only semantics, returned data, side effects, or permissions. This falls far short of what a delegated system tool should disclose.

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 short, but it wastes its only sentence echoing the tool name and the generic 'Apple-Tools-MCP' wrapper. This is under-specification rather than effective conciseness.

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?

Despite having an output schema, the description gives no operational context, no input explanation, no example, and no relationship to the broader preference-reading toolset. An agent would have to guess the meaning of the domain parameter and the function of current_host.

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 0%, and the description names neither parameter. 'domain' and 'current_host' are left completely unexplained, with no indication of what values are expected or how current_host modifies behavior.

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 restates the tool name ('system_read_preference_domain') without explaining what reading a preference domain actually does or what kind of resource it operates on. 'Delegated Apple domain tool' adds no functional meaning and fails to distinguish this from related preference tools like apple_get_preferences or system_list_settings_domains.

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?

There is no guidance on when to use this tool, what problem it solves, or when to prefer a sibling tool. The description provides zero context about selection among the many preference-related tools in the sibling list.

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