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

readOnlyHint=true already declares this as a safe read, and 'Read-only.' merely restates that annotation rather than adding to it. The enumerated settings list does add useful behavioral context about what the call surfaces, but there is no mention of permissions, error behavior, or defaults for unset settings. Given annotation coverage, a 3 is appropriate.

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?

One dense front-loaded sentence naming the resource followed by the returned field set, plus a two-word safety tag. Every clause earns its place; nothing is padded or redundant beyond the minor restatement of readOnlyHint.

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 no output schema, the description usefully enumerates the returned fields, which is exactly the compensating detail needed. Combined with 100% schema coverage for both required params and readOnlyHint, an agent has enough to invoke it correctly; only edge-case behavior (unset settings, permission requirements) is unaddressed.

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%: addon_name and cluster_id are both documented in the schema, including the pointer to list_clusters for discovering ids. The description adds nothing about parameter format or semantics beyond the schema, so the baseline of 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 ('Get an installed addon's operational settings on the cluster') and enumerates exactly which settings are returned (sync policy, sync window, retry policy, ignore-differences rules, revision history limit, strict health check, rollback-on-failure, keep-failed-resources). This field-level specificity cleanly separates it from siblings like get_addon_configuration, get_addon_details, and get_addon_status without needing to name 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?

Usage is implied by the content (read operational settings for an installed addon), but there is no explicit when-to-use guidance, no statement of prerequisites, and no routing to the many nearby siblings (get_addon_configuration, get_addon_details, get_addon_status, get_addon_history). The agent must infer which addon-read tool fits its need.

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