Get the App Privacy label steps

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description earns extra credit by disclosing behavior beyond that: Apple does not expose this via API, the return is step-by-step instructions plus a deep link, and the tool is gated to Pro users — all non-obvious traits an agent needs.

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 short, front-loaded sentences with no padding; the API limitation and return behavior come early. Only the mildly misleading opening verb costs it a point.

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?

With no output schema, the description correctly fills the gap by describing what comes back (steps + deep link). All required/optional parameters are covered by the schema, and the Pro restriction is noted, so an agent can call it correctly; explicitly resolving the read-only-vs-configure ambiguity would make it airtight.

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 are already documented with patterns and descriptions, giving a baseline of 3. The description's note about data_not_collected:true largely restates the schema's own wording and adds no format or edge-case detail beyond it.

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 the resource (App Privacy nutrition label) and the real outcome (returns the exact steps + deep link, since Apple does not expose it via API). The leading verb "Configure" is slightly misleading given the tool is read-only, but the very next clause corrects it, so an agent still lands on the right purpose without opening the schema.

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 one concrete branch rule (pass data_not_collected:true for the 'Data Not Collected' path) and flags the Pro gate, which is useful. However it offers no when-to-use vs alternatives or when-not guidance, and no sibling (e.g. asc_guide) is named, so routing is only implied.

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