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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: it returns a comprehensive bundle of files, hashes, dependencies, permissions, install steps, and constraints. It also warns that some install steps need a human in Xcode or a provider console, which is a real behavioral constraint beyond the annotations.

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 long but information-dense, and it front-loads the critical usage instruction ('Use this before touching a native project'). Every clause adds a distinct piece of information about what the kit includes. It is somewhat verbose, but the density justifies the length.

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 read-only retrieval tool with one parameter and no output schema, the description is remarkably complete. It tells the agent what the returned kit contains, what to do before calling, and what constraints to expect. The only minor gap is not describing the exact output format, but the description's enumeration of contents compensates for the missing 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?

Schema coverage is 100% and the only parameter 'id' is described with an example ('e.g. background-location'). The description doesn't add much about the parameter itself, but with full schema coverage and a single simple parameter, the baseline of 3 is appropriate.

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 ('get') and resource ('a TrustyCap Native Kit'), and immediately distinguishes it from siblings by saying 'Use this before touching a native project, once a kit has been chosen.' It also contrasts with reverse-engineering, making the tool's purpose unmistakable.

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 explicitly says when to use it ('before touching a native project, once a kit has been chosen') and implies when not to use it (before a kit is chosen, presumably use list_native_kits or guide). It also names the alternative behavior (reverse-engineering) that this tool avoids, giving clear context.

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