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

Annotations declare readOnlyHint=true, so safety is already covered; the description reinforces it ("Read-only") and adds richer context: each entry carries the resource key, kind, both change types, and resolution state, plus the semantic that a recorded 'git'/'cluster' choice converges on the next sync. That return-shape detail is meaningful since no output schema exists.

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?

Three tightly written sentences: purpose first, then output content, then usage ordering. No filler, and the most decision-relevant information (what a conflict is, use it first) is front-loaded.

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?

Without an output schema, the description carries the burden and does so: it explains what is listed, what each entry contains, the resolution-state semantics, and the read-only nature. Nothing an agent needs to invoke it correctly is missing.

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% and the single optional cluster_id parameter is fully documented in the schema (including the chat-scoped fallback). The description adds no syntax or format detail beyond that, so 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?

States a specific verb and resource (list open GitOps merge conflicts on a cluster) and then defines what a conflict actually is: resources changed in both Git and the cluster record since the last sync. An agent can differentiate this from get_gitops_status and get_gitops_conflict_diff from the description alone.

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?

"Use this first to see what conflicts exist before inspecting diffs or resolving" gives explicit ordering relative to the sibling tools get_gitops_conflict_diff and resolve_gitops_conflict. The alternatives are described by activity rather than named, so it stops just short of fully explicit routing.

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