set_export_compliance

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

Discloses that it modifies export compliance status, which aligns with destructiveHint=false and readOnlyHint=false. However, does not discuss reversibility or side effects on existing submissions, but the mutation is straightforward.

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 well-structured sentences with no fluff. First sentence states purpose, second gives context, third provides practical guidance. Front-loaded effectively.

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?

Provides sufficient context for a simple boolean setter with three parameters, including workflow relevance and parameter defaults. Could mention what happens after setting but not critical given no output schema.

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?

Adds meaningful context beyond the schema: explains why uses_non_exempt_encryption is needed and when to set true/false, and clarifies default for build_id. Schema coverage is 100%, so description supplements well.

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?

Clearly states the tool sets export compliance declaration for iOS builds, with specific verb 'Set' and resource. Distinguishes from siblings by focusing on a compliance step not covered by other tools.

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?

Explicitly states when it's required (before App Store submission and TestFlight external distribution) and provides guidance on setting false for most apps vs true for custom encryption. Also explains default behavior for build_id parameter.

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