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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the operation's safety profile. The description adds 'immutable' as a property of the data, which is mild useful context, but it does not disclose behavior like ordering, pagination shape, or response content beyond the schema's cursor/limit/detail 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?

The description is a single short sentence with no filler, and the key qualifier 'immutable' is front-loaded. It is appropriately terse given that the input schema documents all parameters, though it is near the lower bound of informativeness.

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 7-parameter tool with no output schema, the one-clause description is enough to identify the basic list operation, and the schema fills parameter semantics. However, it lacks any statement of the return shape, default output behavior, or distinction from close siblings, so an agent must infer significant context from the tool name.

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 100%, so the baseline is 3 even though the description itself names no parameters. The schema's per-parameter descriptions, including id usage, tag/topic slug constraints, cursor handling, and detail enum meanings, carry the semantic burden effectively.

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 ('List') and a specific resource ('immutable knowledge versions'), which clearly indicates a read-only history operation. It does not explicitly distinguish itself from closely related siblings like list_space_entry_versions or get_sync_changes, so it falls short of a 5.

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?

There is no guidance about when to use this tool versus alternatives such as list_space_entry_versions, get_space_changes, get_sync_changes, or get_knowledge. The only implied usage clue is the phrase 'knowledge versions', which is not enough to make a confident selection decision.

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