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

The description adds real context beyond annotations: it makes explicit that the entire profile is replaced (consistent with destructiveHint=true) rather than merged, and it gives actionable retry guidance by pointing at idempotencyKey as the remedy for the non-idempotent default. It does not describe what happens to omitted optional fields or whether the overwrite is recoverable, which would have pushed it higher.

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 short sentences, front-loaded with the overwrite semantics and the retry caveat. Nothing is padded, though "Step 2: Teach it the business" is more flavor than specification given how much parameter explanation is missing.

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?

This is a large, deeply nested replacement payload with no output schema and almost no schema-level parameter descriptions, yet the description is three sentences with no field guidance, no partial-vs-full example, and no note on validating required sub-objects like address or vibe. For a destructive full-overwrite tool of this complexity, that is materially incomplete.

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?

With 24 parameters and only 8% schema description coverage, the description carries almost the entire semantic burden — and it explains none of them. The complex nested payloads (vibe, hours.regular/exceptions, evidence statuses, documents, escalationContacts, staff) are entirely undocumented in prose, and the one mention of idempotencyKey largely restates the schema's own 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?

"Replace the whole knowledge profile the AI receptionist answers from" gives a specific verb (replace/put) and resource (knowledge profile), and the word "whole" signals full-overwrite semantics that distinguish it from ringkit_patch_knowledge. It stops short of naming the sibling tool explicitly, so the contrast is inferred rather than stated.

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?

"Step 2: Teach it the business" positions the call in the setup flow, which is genuinely useful ordering context. However, it never names alternatives (patch_knowledge, import_knowledge, set_knowledge_tier) or states when a caller should prefer a partial update over this full replacement, leaving the selection logic implicit.

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