Summarize a build directory's model

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe local read. The description adds the content inventory of the summary, but says nothing about cost, size, or the fact that it may auto-select a build directory when buildDir is omitted (that detail lives only in the schema).

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?

A single front-loaded sentence that lists the payload contents without filler. Every clause earns its place; nothing is repeated from the schema or annotations.

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 what the summary returns, and the read-only annotation covers the safety profile. Adequate for a zero-required-parameter read tool, though it omits any hint about relative cost versus the finer-grained sibling tools.

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 both parameters are documented there (including the single-build-directory fallback and the multi-config default). The description adds no parameter-level meaning beyond the schema, 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-and-resource pair (high-level overview / build directory) and enumerates the contents (CMake version, generator, configurations, project() hierarchy, target names by type), which implicitly separates it from list_targets and get_cache_variables. It does not explicitly name a sibling to contrast against, keeping it at 4 rather than 5.

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?

"High-level overview" implies this is the orientation/entry-point tool before drilling into specific data, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. "use list_targets for per-target detail"). Usage is inferable but not spelled out.

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