auto-install

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

With no annotations, the description carries the full burden. It discloses idempotency, the need for an IDE restart, and the follow-up call to ack-restart. It could elaborate on error scenarios or permissions but is largely transparent.

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 front-loaded with the important use case and flows naturally from action to idempotency to usage steps. It is slightly verbose but each sentence adds value, so it's well-structured.

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?

The description covers the install action thoroughly but ignores the 'check' action for drift reports, which is defined in the schema. It also lacks information about return values or output, which could be helpful since there is 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?

Schema coverage is 100%, so the baseline is 3. The description does not add extra meaning beyond the schema; it focuses on the overall action rather than individual parameters. No additional clarity on parameters like 'force' or 'action' is provided.

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 explicitly states the tool installs a project kit into the host's native layout, making agents, skills, and commands available. It uses specific numbers (73, 98, 89) and distinguishes from siblings like ack-restart by explaining the post-restart step.

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 clearly says 'Run once per project on first kit-mcp contact' and advises restarting the IDE and calling ack-restart afterward. However, it does not differentiate between this tool and the sibling tool named 'install', which could cause confusion about which to use.

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