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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so safety is covered. The description adds useful context with 'safe source metadata' (implying filtered/redacted output) and the five-revision cap tied to 'active' revisions, but it doesn't say what happens when a ref is inactive or invalid.

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?

A single tight sentence with the scope constraint front-loaded and no filler. Nothing superfluous, though it is arguably too terse to carry the semantic load given the 0% schema coverage.

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?

An output schema exists, so return values needn't be described, and annotations cover the safety profile. Still, for a tool whose parameter is entirely undocumented, the description omits failure behavior for non-active or missing revisions, leaving an agent with unanswered edge-case questions.

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 0% on the single required parameter, so the description must compensate. It only restates the maxItems constraint ('up to five') that the schema already enforces and hints that refs point at revisions; it never clarifies that refs are UUIDs or what constitutes a valid/active revision.

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?

Specific verb ('Return') plus resource ('source metadata for knowledge revisions') with a stated scope constraint ('up to five active'). It is reasonably distinguishable from siblings like query_domain_knowledge or describe_knowledge_domain, though it doesn't explicitly contrast itself with them.

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?

No when-to-use guidance, no prerequisites, and no mention of an alternative tool. The only guidance is the implicit constraint that targets are 'active' revisions, which is a scoping detail rather than usage direction.

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