add_knowledge_base_to_agent

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

Annotations provide readOnlyHint and destructiveHint, which are non-contradictory. Description adds cost warning and allowed types but lacks detail on authentication, rate limits, error behavior, or whether existing knowledge base is overwritten. Output schema exists but is not leveraged.

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?

Description is short with three sections: main action, cost warning, args list. Front-loaded with purpose. Args list is somewhat redundant with schema but not excessive.

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 5 parameters (3 optional, mutually exclusive), the description fails to explain that exactly one of url/input_file_path/text should be provided. Does not state what the knowledge base is used for or potential side effects. Output schema exists, so return values are not required, but the rest is under-specified.

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 has 0% description coverage for parameters. Description lists parameters with one-liners (e.g., 'ID of the agent') that mostly restate property names, adding no substantive semantics. Does not clarify mutual exclusivity of url, input_file_path, text.

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?

Description clearly states 'Add a knowledge base to ElevenLabs workspace' with specific verb and resource. Lists allowed file types (epub, pdf, docx, txt, html), which distinguishes it from sibling tools like create_agent or text_to_speech.

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?

Includes explicit COST WARNING and directive 'Only use when explicitly requested by the user,' providing clear guidance on when to invoke. No sibling tool adds knowledge bases, so no alternative guidance needed.

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