init

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

No annotations are provided, so the description must carry the full burden. It notes that using project_dir does not change the session's base project, which is a behavioral caveat. But it does not disclose side effects, error cases, or resource impact (e.g., file creation).

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 somewhat unstructured, mixing usage patterns and parameter notes. It is not overly verbose but could be more streamlined. The front-loaded purpose is clear.

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 presence of an output schema, return values are covered. However, the description lacks completeness on prerequisites, error handling, or how init fits into the larger tool ecosystem. It gives enough for basic use but not full 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?

With 0% schema description coverage, the description compensates by explaining blueprint (applies a blueprint) and project_dir (sets up in another folder, boundary effect). It omits the help parameter, but the other two are clarified beyond schema defaults.

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 tool initializes .linklore and starts local footprint memory. It provides usage patterns (basic and with blueprint). However, it does not explicitly distinguish from sibling tools, but the unique function is evident.

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 mentions that setting up in another folder via project_dir is init-only and that to persist working there one should use config(action='pin'). However, it lacks explicit when-to-use or when-not-to-use guidance relative to siblings like config or doc_setup.

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