What does this config setting do?

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, destructiveHint=false, so safety is covered externally. The description adds that answers come from the 'official schema' and what facets are surfaced, but says nothing about auth, rate limits, or resolution behavior when a schema URL is fetched. With annotations carrying the safety profile, this is adequate but shallow.

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?

Roughly three dense sentences, front-loaded with the core purpose, then the setting-path semantics and the search alternative. Examples earn their space by showing path syntax; no filler.

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, so return shape need not be re-explained, and the description still lists the facets exposed. Combined with the dotted-path and search guidance, an agent has enough to call this correctly; only sibling differentiation (find_schema) 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 only 33%, so the description must compensate, and it does: it defines `setting` as a dotted path with three concrete examples (compilerOptions.module, jobs.*.runs-on, services.*.healthcheck), explains the omitted-setting default, and documents the `search` alternative with an example query. Only the `schema` parameter is left to the schema itself, which already describes it.

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+resource: it explains what a config setting 'means and accepts' from its official schema, and enumerates what is returned (description, type, allowed values, default, deprecation, sub-settings). It does not, however, differentiate itself from the sibling find_schema, whose purpose overlaps (locating schema info).

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?

The description distinguishes its two access modes clearly – a dotted-path lookup with the `setting` parameter versus word-based discovery via `search` – and notes omitting `setting` returns the top level. It gives no guidance on when to prefer this over find_schema or validate_config, so usage is implied rather than explicitly routed.

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