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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description's genuinely additive contribution is "No source access grant or execution" – clarifying that reading the graph does not require or trigger access to the underlying source – plus the "currently visible" qualifier implying permission-filtered results. That is real but thin context beyond the annotations.

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?

Two compact sentences with the core action front-loaded and no filler. Brevity here slightly hurts clarity, but nothing is redundant or padded.

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 and annotations are rich, so return values and safety need not be described. However, for a tool sitting among five similarly named connection siblings, the description omits the routing information an agent needs most to invoke it correctly.

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 coverage is 100%, and the schema already documents that id is a graph UUID returned by connections.backfill and not a credential ID. The description adds nothing further about the parameter, so the baseline 3 applies.

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?

"Read canonical connection references and currently visible exact resource revisions" names a verb (read) and a resource (connection references/revisions), but the phrasing is jargon-heavy and abstract. It does not differentiate from connections_list, connections_roots, or connections_catalog, so an agent can't tell from the description alone which of the connection tools to pick.

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 statement of when to use this tool versus the many sibling connection tools, nor any prerequisite or exclusion beyond the trailing caveat. The reader is left to infer usage entirely from the schema's hint that the id comes from connections.backfill.

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