import_public_brain

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

Discloses non-destructive nature, return values, and valid frameworks. Without annotations, this provides substantial behavioral context, though missing auth or rate limit info.

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?

Two concise paragraphs: first covers behavior and returns, second covers usage guidance. No wasted words, well structured.

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?

Covers purpose, parameters, behavior, return values, usage context, and sibling references. No output schema, but return described sufficiently.

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?

Description adds value beyond schema by listing valid frameworks (enum-like) and noting default for limit. Schema coverage is 100% so baseline 3, but useful extra context.

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?

Clearly states 'Import community lessons from the Cachly Public Brain for a framework' with additional details like non-destructive behavior and return values. Distinguishes from siblings such as publish_lesson and learn_from_attempts.

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?

Explicitly recommends using this tool to bootstrap a new brain before first session_start, and points to alternatives (publish_lesson, learn_from_attempts) for other tasks.

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