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

No annotations are provided, so the description carries the full burden of disclosure. It indicates a mutation ('add') but says nothing about permissions, whether indexing is synchronous, limits on content size, or what happens if a knowledge source with the same name already exists.

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?

A single front-loaded sentence with no filler. Every word contributes to the stated purpose, and the accepted content types are mentioned immediately.

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?

There are no annotations, no output schema, and zero schema description coverage, yet the description is only one sentence. For a three-parameter mutation tool, it should clarify required parameters, effects on the knowledge base, and how this differs from the related upload and crawl tools.

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 description coverage is 0%: the parameters bot_id, name, and content are only labeled with titles. The description gives a vague hint that content is a text snippet or Q&A document and that bot_id targets a chatbot, but it never explains the role of 'name' or any format expectations, so it does not compensate for the missing schema documentation.

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 states a clear verb+resource (add knowledge to a chatbot) and distinguishes the accepted content types (text snippet or Q&A document). It does not explicitly name or differentiate from the close sibling upload_knowledge_document, so it falls short of a 5.

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 phrase 'text snippet or Q&A document' implies this is for inline text rather than file uploads, which gives some usage guidance. However, it never states when to use this versus upload_knowledge_document, crawl_website_knowledge, or sync_cloud_storage, nor does it mention prerequisites or exclusions.

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