adopt_existing_project

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states the scan and generate actions and lists outputs, but it does not disclose side effects like file writes, permission requirements, or whether the operation is read-only or destructive. This is a notable gap but not misleading.

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 a single sentence with no redundant words, efficiently front-loading the core function and its expected outputs. Every word earns its place.

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 main purpose and explicitly lists the outputs, and an output schema is present to document return values. However, it omits side effects and prerequisites (e.g., whether it modifies the codebase), so it is mostly complete but lacks some operational context.

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?

The schema has one optional parameter 'path' with default '.', but the description does not mention it or add any meaning beyond the schema. With 0% schema description coverage, the description fails to compensate for the missing parameter explanation, leaving the agent to infer that 'path' refers to the codebase location.

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 uses specific verbs 'Scan' and 'generate' with a clear resource 'existing legacy codebase' and lists four distinct output artifacts (context, PRDs, milestones, audit tasks). This clearly distinguishes it from sibling tools like bootstrap_project, which are for new projects.

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 implies the tool is for existing legacy codebases but does not explicitly state when to use it versus alternatives such as bootstrap_project or create_project_workspace. No exclusions or alternative tool names are mentioned, leaving the usage context only implied.

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