apple_create_accessibility_declaration

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

No annotations are provided, so the description carries the full behavioral burden for a mutating tool. It only says a declaration is created and does not disclose permission requirements, whether existing declarations are replaced, how omitted boolean fields are treated, or what the response contains.

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 front-loaded sentence with no redundant or wasted text. It immediately establishes the core action, resource, and scope.

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?

This is an 11-parameter mutation tool with low schema description coverage, no annotations, and no output schema. The description is far too thin to compensate for those gaps, leaving the agent without enough context to confidently populate the boolean accessibility fields.

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 only 18%, and nine boolean parameters have no schema descriptions at all. The tool description mentions only the app and device family at a conceptual level, leaving parameters such as supportsCaptions, supportsVoiceover, and supportsDifferentiateWithoutColorAlone unexplained beyond their names.

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 states a specific verb (Create), resource (accessibility nutrition label declaration), and scope (app on a specific device family). It is clear what the tool does, though it does not explicitly distinguish itself from sibling tools such as apple_update_accessibility_declaration or apple_list_accessibility_declarations.

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 explicit guidance on when to use this tool versus updating, listing, or deleting accessibility declarations. The word 'Create' implies a new declaration, but the description does not mention prerequisites, when not to use it, or which sibling tool handles existing declarations.

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