Open-Brain

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool imports data but doesn't describe what happens during import (e.g., whether it overwrites existing data, requires authentication, handles errors, or has rate limits). For a tool with zero annotation coverage and an implied mutation operation, this is a significant gap in transparency.

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 concise—a single sentence that directly states the tool's purpose with no fluff. It's front-loaded with the core action and includes examples of external platforms for clarity. Every word earns its place, making it efficient and easy to parse.

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 implied complexity (importing from external platforms likely involves authentication, data transformation, and potential side effects), the description is incomplete. With no annotations and no output schema, it doesn't explain what the tool returns, how errors are handled, or any behavioral nuances. For a tool with zero structured coverage, this minimal description is inadequate.

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 schema description coverage is 100%, so there are no parameters to document. The description appropriately doesn't waste space on parameter details. It earns a 4 because it correctly focuses on the tool's purpose without unnecessary parameter explanations.

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's purpose as importing runbooks from external platforms, specifying both the action (import) and the resource (runbooks from Notion, Obsidian, Readwise, etc.). It distinguishes itself from siblings by focusing on external data import rather than internal operations like search, update, or analysis. However, it doesn't explicitly mention what happens after import or how it integrates with the system.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing credentials for external platforms), when not to use it, or how it relates to sibling tools like 'capture_thought' or 'update_thought'. The agent must infer usage from the purpose alone.

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