import_public_brain

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

No annotations provided, so description carries full burden. It discloses non-destructive behavior (existing lessons with same topic key not overwritten), specifies return values (count and topic slugs), and lists available frameworks. No contradictions.

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?

Description is efficient: one sentence for main action, one for behavior/return, one listing frameworks, one for usage context, and two for sibling alternatives. No wasted words, front-loads key information.

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 has no output schema, the description explains return values. Covers import source, non-destructive behavior, framework list, usage timing, and sibling tools. Complete for correct selection and basic 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?

Schema coverage is 100%, so baseline is 3. Description adds value by listing all available frameworks and noting the default limit value (20), which is not in schema. This compensates slightly above baseline.

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 imports community lessons from the Cachly Public Brain for a specific framework, with a specific verb ('Import') and resource. It distinguishes from sibling tools like 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 states when to use: 'bootstrap a new brain... before your first session_start'. Also provides clear alternatives: 'Use publish_lesson to contribute... use learn_from_attempts for storing lessons from your own sessions.'

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