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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, and readOnlyHint=false. The description adds useful context that local company policies and prior agent snapshots are preserved, and that company-admin authority is required, but it does not explain what the destructive consequence actually is or how conflicts/revisions are handled.

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?

The description is compact and front-loads the operation and key constraints. The first sentence largely restates the title, but the second sentence adds meaningful behavioral context without excessive length.

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 destructive, open-world mutation with five required parameters, low schema coverage, and no output schema. The description covers some authority and preservation behavior but leaves major gaps around profile semantics, revision conflicts, idempotency, and expected results.

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 only 17%, so the description must carry more semantic weight. It hints at version, expectedRevision, and reason, but does not explain profile formatting, company UUID requirements, idempotency_key usage, or revision conflict semantics.

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 specific verb and resource: adopt an exact published shared version. It is clear what operation is performed, though it does not explicitly distinguish this tool from siblings such as summer_knowledge_adoptions, summer_knowledge_shared_publish, or summer_knowledge_shared_review.

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 'company-admin authority' implies a prerequisite, and 'expected adoption revision' implies optimistic concurrency, but there is no explicit guidance on when to use this versus related knowledge tools. No alternatives or when-not-to-use conditions are named.

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