add_knowledge

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that it adds a knowledge entry, but provides no details on idempotency, requirements (e.g., active session/project), return values, error cases, or whether duplicates are checked. This is a significant gap for a write operation.

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 a single sentence that front-loads the action and purpose. Every word serves a function, and there is no wasted text or redundant phrasing.

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?

For a tool with 5 parameters, no output schema, and no annotations, the description is too minimal. It does not explain what happens after adding (e.g., return value, ID), any prerequisites like an active session/project, or how to handle potential errors. The presence of sibling tools like start_session and setup_project suggests dependencies that are not mentioned.

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 input schema already covers 100% of parameters with descriptions, so the baseline is 3. The description does add context about content types (insights, tips, best practices) that aligns with the category enum, but it does not add extra meaning beyond what the schema provides.

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 uses a specific verb ('Add') and resource ('knowledge entry to RAG'), and lists the types of content intended ('insights, tips, best practices, and lessons learned'). This clearly distinguishes it from sibling tools like update_knowledge or delete_knowledge.

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 implies usage when you want to store new knowledge, but it does not explicitly mention when to use this tool instead of update_knowledge or search_knowledge. No exclusion criteria or alternative tools are named, so the guidance is only at an implicit level.

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