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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds real value by disclosing what is NOT provided ('The packaged source itself is not distributed yet, and no kit carries a price') and that install steps include human-in-the-loop actions in Xcode or a provider console. This tells the agent what to expect and what to warn the user about.

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 manifest contents are front-loaded early, which is good, but the description is an unbroken enumerated list with the instruction 'before touching a native project' repeated at both the start and the end. That repetition costs space without adding meaning, making it longer than it needs to be.

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?

There is no output schema, so the description must carry the return-shape burden, and it does so thoroughly — enumerating file source with hashes and production paths, pinned dependencies, permissions and entitlements with failure modes, the JS interface, immutable config, ordered install steps, and proven constraints. An agent knows what it will receive before calling.

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?

With a single id parameter at 100% schema coverage, the schema already documents the field including an example ('background-location'). The description adds no format, naming, or lookup guidance beyond the schema, so the baseline of 3 applies.

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 and resource ('One Native Kit's full manifest') and enumerates exactly what that manifest contains, so an agent knows this retrieves one kit's packaged documentation rather than listing kits. It is distinguishable from siblings like trustycap_list_native_kits, though it never names them directly.

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?

It gives clear use context — 'Use this before touching a native project, once a kit has been chosen' — which implies the kit must already be selected (via a sibling listing tool) and that this must be read before modifying a project. It offers no explicit when-not or named alternatives, but the prerequisite condition is well stated.

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