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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds no behavior beyond that — it says nothing about ordering, recency, pagination/limits, what constitutes a revision, or what fields a revision record contains.

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?

At nine words there is no waste, but the terseness is under-specification rather than efficiency: a sentence fragment with no verb does not front-load the action the agent is selecting. Slightly more structure would cost little and clarify considerably.

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?

There is no output schema, so the description carries the burden of explaining what a revision listing returns, and it does not. For a tool sitting in a dense cluster of revision-related siblings, the definition leaves the agent unable to predict results or know whether a call is sufficient versus needing compare_saved_versions.

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 a single parameter and 100% schema description coverage, the schema already explains that source_id is the src_... identifier obtained from list_event_connections. The description mentions 'a source' but adds no format, validation, or edge-case meaning beyond that.

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 phrase 'The saved versions of a source's configuration' identifies the resource (revisions of a source's config) but is a bare noun phrase with no verb, so it never says the tool lists them. It also fails to distinguish this from siblings like list_saved_versions, preview_saved_version, or compare_saved_versions, which operate in the same revision space.

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 when-to-use guidance and no exclusions. Given siblings such as list_saved_versions, compare_saved_versions, and preview_saved_version, an agent has no stated basis for choosing this tool over them; the only signal is the schema's reference to list_event_connections for obtaining source_id.

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