knowledge_search

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

The description explains that keywords are automatically extracted from ledger and handoff entries, and lists available categories. It does not contradict any annotations (none provided) and provides good insight into behavior beyond the schema.

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 concise and well-structured, with a main paragraph explaining purpose and a list of categories. Every sentence adds information without redundancy.

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 complexity (6 parameters, nested object) and no output schema, the description covers the tool's capabilities well. It explains search behavior, categories, and optional features, though detailed output format is not described.

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 the baseline is 3. The description adds value by explaining spreading activation in plain language and highlighting the trace option, which goes beyond the schema's technical descriptions.

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 searches accumulated knowledge across sessions using keywords, category, or free text. It distinguishes itself from other search tools by emphasizing cross-session search and automatic knowledge base growth.

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 specifies using this to find related past work, decisions, and context from previous sessions. It does not explicitly mention when not to use or alternatives, but the context is clear enough for an agent to infer appropriate usage.

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