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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds genuinely non-obvious context: a KB can be shared across multiple agents, the change propagates to all of them, and it is refused with a specific 403 shared_with_other_agents unless the key can act on every consuming agent. That is meaningful disclosure beyond structured fields.

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?

Front-loaded with the core semantics before the sharing/error caveat. The opening restates the title verbatim, which is mildly redundant, but the body is dense and earns its sentences.

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 destructive, no-output-schema mutation tool with 5 params, the description covers the overwrite scope, the cross-agent propagation risk, and the 403 refusal condition. It does not state the return shape, but with no output schema that gap is minor.

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 60%, and the description compensates by clarifying the tags parameter's conditional behavior ('changes only when sent') and the overwrite semantics of name/content. The rich content and agent/knowledge_base_id error semantics live in the schema, so the description adds value mainly for tags and replacement scope.

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 (replace) and resource (knowledge base) and clarifies the exact semantics: name and content are overwritten, tags only when sent. This distinguishes it from create_knowledge_base and get_knowledge_base, though the siblings are never named explicitly.

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 when this applies (full replacement of an existing KB) via the tags rule, but gives no explicit when-to-use versus update/create guidance or prerequisites beyond the error conditions. Usage is inferable but not spelled out.

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