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 covered structurally. The description adds useful side-effect context — that no source access grant is issued and no execution is triggered — and 'currently visible' implies permission-filtered results, but it says nothing about pagination, limits, or result shape.

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 zero filler, and the read scope is front-loaded before the boundary clause. Every clause carries meaning.

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?

With an output schema present, return values need not be explained, and annotations plus a fully documented parameter cover the mechanics. The remaining gap is routing: nothing tells an agent why to pick this over connections.list or baseline.lineage.

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%: the single 'id' parameter is already documented as a stable graph UUID returned by connections.backfill rather than a credential ID. The description adds no syntax, format, or sourcing detail beyond that, 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?

The description names a specific verb ('Read') and concrete resources ('canonical connection references', 'currently visible exact resource revisions'), so an agent can tell this is a graph-read operation rather than a listing or lineage call. It does not, however, distinguish itself from nearby siblings such as connections.list, connections.catalog, or baseline.lineage.

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?

Usage is only implied by the verb 'Read' plus the closing boundary 'No source access grant or execution', which signals a non-mutating inspection context. There is no explicit when-to-use statement, no prerequisites, and no named alternative for cases where the agent needs listing, catalog, or lineage instead.

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