memory_attach_project

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

With no annotations, the description carries full burden. It discloses 'Auto-activates on success' (a behavioral trait), but fails to describe other important behaviors: side effects (e.g., does it modify files?), required permissions, reversibility, or error conditions. The single behavioral note is helpful but insufficient for a tool with no annotations.

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 extremely short (two sentences, 11 words). While concise, it is underspecified and lacks structure (e.g., no front-loading of key information, no separation of purpose from usage). The brevity results in missing essential details.

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?

Given the tool's complexity (4 parameters, 0% schema coverage, no annotations, and an output schema that is not described), the description is severely incomplete. It does not explain the return value (even though an output schema exists), parameter semantics, or behavioral context. The agent cannot reliably select or invoke this tool.

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 0%, meaning the schema provides no parameter descriptions. The tool description does not compensate: it does not explain the purpose of any of the four parameters (slug, description, display_name, project_path). An agent must guess their meanings from names alone, which may be ambiguous.

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 the verb 'attach' and resource 'existing project directory', which conveys the basic purpose. However, it does not explicitly differentiate from sibling tools like memory_init_project (which creates new projects) or memory_list_projects (which lists projects). The distinction is implied but not stated.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, context (e.g., project must exist), or when not to use it. An agent would have to infer usage from the name alone.

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