Bootstrap repo for Mushi

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

Discloses writing three specific files, idempotency (beyond annotation), required scope (mcp:write), and lifecycle relationship to `mushi sync-lessons`. This adds behavioral value beyond the `idempotentHint` annotation, which only flags idempotency without details.

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?

Three concise sentences cover purpose, files, idempotency, scope, and usage alternatives. No redundant information; every sentence adds value.

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 bootstrap tool with one optional parameter and no output schema, the description fully explains the side effects, prerequisite (scope), and post-usage steps. It provides a complete picture of how this tool fits into the workflow.

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 baseline is 3. The description does not elaborate on the `projectId` parameter beyond its schema description ('Project UUID — defaults to configured project'). No additional meaning is added, but the schema alone is sufficient given the optional default.

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 clearly states it writes three specific bootstrap files (`.cursorrules`, `.mushi/lessons.json`, `MUSHI.md`) and briefly explains each. This distinguishes it from siblings like `list_lessons` or `query_lessons` by specifying exactly what files are created and that it's a one-time setup 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?

Provides explicit guidance: 'Call this once after connecting the repo; subsequently use mushi sync-lessons from CI.' Also notes idempotency and safe re-running, giving clear when-to-use and when-not-to-use context.

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