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

Annotations already declare the write/non-destructive/openWorld profile, so the bar is lower, and the description adds genuinely new behavior: the tool may return a `needs_confirmation` envelope, which explains the approvalId parameter path. It does not state permission requirements, name-collision behavior, or default visibility (left to 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?

Three sentences, front-loaded with the core action, then recipe selection, then the follow-up pipeline. Every clause carries unique information; the trailing note about needs_confirmation is terse but operationally relevant rather than filler.

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?

With six parameters, no output schema, and only weak annotations, the description covers creation semantics, variant choice, follow-up steps, and the deferred-confirmation path. It omits what the call returns (e.g. the new KB identifier) and any naming/permission constraints, which an agent would still need to guess.

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 83%, so baseline is 3, and the description earns above that by explaining what each recipe produces ('tabular' data queried with SQL, 'graph' entity/relationship extraction) and by tying the confirmation envelope to the approvalId flow. name, workspace, and description parameters gain no further meaning from the description.

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?

States a specific verb and resource ('Creates an empty knowledge base') and immediately differentiates the three variants of that resource via recipe semantics. An agent can distinguish this from workbench_kb_add_documents, workbench_kb_get, or workbench_kb_search without opening any schema.

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?

Gives concrete downstream pipeline guidance: add content with workbench_kb_add_documents, then attach to an agent flow with workbench_flows_attach_knowledge_base before publishing. It does not say when *not* to use this tool (e.g. if a KB already exists, or workspace constraints), so it stops short of full routing guidance.

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