install_agentic_kit

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

With no annotations, the description carries full burden and does well: it discloses idempotency (re-running updates to the MCP version), non-destructive default behavior (files not installed by this MCP are respected unless overwrite=true), and marker-scoped editing of AGENTS.md so the rest of the file is untouched. It omits any mention of permissions or what the call reports back.

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?

Information is front-loaded: what gets installed first, then the idempotency/overwrite contract, then the usage trigger. It is dense but nearly every clause carries distinct operational detail; only the file enumeration is slightly long.

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 3-parameter mutation tool with no output schema, the description covers target files, safety behavior, and the select-the-orchestrator detail that matters when calling it. Missing only return/report information and permission expectations.

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 the schema already documents all three parameters including the models defaults and the overwrite semantics. The description reinforces the overwrite rule consistently with the schema but adds no extra syntax or constraint detail beyond it, making the baseline of 3 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?

States a specific verb (installs/updates) plus an enumerated resource list (middleware agents, spec template, AGENTS.md section), leaving no ambiguity about what gets written. It does not explicitly name a sibling to distinguish against, but the scope (repo bootstrap) is clearly different from scaffolding-oriented siblings.

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 closing sentence gives a clear trigger: use it when the user wants the repo ready to create services with the MCP. It also implies a precondition via 'repo consumidor'. No explicit when-not or named alternative (e.g., scaffold_service) is given.

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