email_mobileconfig

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

With no annotations, the description carries the full transparency burden, and it only names the output artifact. It does not say whether the call is read-only, whether it generates or downloads the file, whether it modifies account settings, or what side effects (if any) occur.

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 short, front-loaded phrase with no filler, so it is easy to parse. However, it is under-specified as a bare noun phrase and could add a verb or a safety note without sacrificing 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?

Given zero parameters and an existing output schema, the mechanical invocation is simple and the return value may be documented elsewhere. Still, the absence of any action verb or behavioral notes means the description is not fully complete on its own.

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?

There are zero parameters and an empty input schema, so there is no parameter documentation needed. The 'current email account' phrase provides the relevant session-based context, which is sufficient for a no-argument call.

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 identifies a concrete artifact ('Apple mobileconfig') and a scope ('current email account'), which implies a retrieval/generation purpose, but it never states an explicit verb or action. his is clearer than a bare tautology but still leaves whether it creates, returns, or manages the profile to inference.

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?

Usage is only implied: a caller would use this when an Apple mobileconfig for the current email account is needed. It does not explicitly state when to choose it over related email or config tools, nor does it mention exclusions or prerequisites.

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