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

With no annotations provided, the description carries the transparency burden. It adds useful behavioral context by stating that no automation session is required and 'Get' implies a read-only operation. However, it does not disclose potential side effects, permissions, connectivity assumptions, or return format, leaving notable gaps.

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 a single well-front-loaded sentence that states the action and scope first, then includes the one critical usage qualifier. There is no redundancy or wasted text.

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 low-complexity tool with one well-documented parameter and no output schema, the description adequately covers purpose, scope, and session requirements. It does not explicitly describe the return data shape, but the enumerated categories give enough expectation for an agent to 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 coverage is 100% and the only parameter, udid, is already described as 'iOS device UDID'. The description adds no further semantic detail, format constraints, or clarification, so the baseline score of 3 applies.

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 a specific verb ('Get') and resource ('device diagnostics') and enumerates battery, HDMI, and WiFi, making the tool's scope immediately clear. It also distinguishes this from narrower siblings like ios_battery or ios_device_info by indicating it is a combined diagnostic call.

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 provides a clear usage condition: 'No automation session required' tells agents when this tool is appropriate as a standalone call. It does not explicitly name sibling alternatives or exclusion cases, so it stops short of full guidance.

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