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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally. The description adds real behavioral context on top: the read/run mode fork and the downstream tool each mode implies, plus the guarantee that changes are 'always the latest version'. It does not discuss auth requirements beyond the draft-version caveat, which the schema already carries.

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?

Front-loaded with the usage trigger, and every clause carries content — the returned-fields list is dense but purposeful. It is longer than strictly necessary and the trailing 'Finally, explain it in plain words' instruction feels appended rather than integrated.

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?

An output schema exists, so the description is not obligated to enumerate return values, yet it covers the workflow from retrieval through use and buying, which is what an agent needs to sequence calls. The lingering 'mode' phrasing is the one spot where an agent could misread a returned field as an input.

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 100%, so both ref and version are already documented in the schema (including the draft restriction), and the description adds no syntax or format detail beyond them. Its 'mode' sentence initially reads like an input parameter even though no such field exists in the schema, which adds mild ambiguity rather than clarity.

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 names the resource (a kit, identified by a ref or CloneKit link) and enumerates what it returns — file index, entry file, review, understand, tools, pricing, license, badges, provenance, recent changes. It also distinguishes itself from the sibling search_kits with an explicit exclusion. It stops short of a single clean verb+resource statement, but the scope is 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?

Explicit trigger ('when the user picked a kit, or gave you a ref or a CloneKit link, before you use or buy it'), an explicit counter-case ('Not for finding kits: search_kits'), and a named workflow for what to do after (read via get_file, or run via start_run). Nothing about when to reach for this tool is left to inference.

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