init_library

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

With no annotations provided, the description carries the full behavioral burden, and it succeeds: it discloses that the tool creates persistent resources, that initialization is permanent, and that calling it multiple times is safe because it will skip if already initialized. It does not claim read-only behavior or hide its mutating nature.

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 appropriately structured with a one-sentence summary, explicit trigger lists, and a do-not-call list. Every sentence adds operational value and the most important guidance ('Call this ONCE') is front-loaded.

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 zero-parameter init tool with no output schema, the description covers everything an agent needs: when to invoke it, what it does, what resources are created, and its idempotent behavior. There is no missing context that would prevent correct invocation.

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 tool has zero parameters and the input schema is empty, so there is nothing to document. The description correctly avoids inventing parameter details, and the baseline for zero-parameter tools is an appropriate 4.

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 identifies the tool as an initialization step: 'Initialize the OpenLMlib knowledge base' and explicitly states it creates 'the SQLite database, vector index, and required directories.' This distinguishes it from the many sibling tools that operate on an existing knowledge base, and the 'before using any other tools' directive makes its role unmistakable.

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 provides explicit automatic triggers (first use, database errors, user request) and explicit non-triggers ('Normal tool usage', 'Each session start'). It clearly tells the agent when this tool should be called and when it must not be called, which is exactly the usage guidance an agent needs for an initialization-only tool.

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