Metis · Librarian — Create Knowledge Database

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

No annotations provided, so description carries full burden. Discloses that it registers a database layer and that indexing requires a separate step. Does not mention idempotency, error behavior, or if overwriting occurs on duplicate slug. Adequate but not thorough.

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?

Brief description followed by usage tip then parameter list. Each sentence adds value. Could be slightly more compact, but overall efficient.

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, and follow-up steps. Has output schema (not shown) so return values are handled. Missing error handling or behavior on duplicate slugs. Adequate for a creation tool with moderate complexity.

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 0%, but description provides detailed explanations for all 5 parameters. Explains slug as URL-safe identifier, layer as 4+ for custom, folders with example. Adds value beyond basic type info.

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?

Clear verb 'Register' and resource 'custom knowledge database layer'. Distinguishes from siblings like build_pdf_knowledge_db which is a follow-up step, but not explicitly compared to other create tools.

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?

Provides sequential workflow: create, then add PDFs, then call build_pdf_knowledge_db. Explains layer numbering (4+ custom). Does not specify when not to use or alternatives, but gives practical context.

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