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 and side-effect profile is fully covered. The description adds the payload's subject matter, but says nothing about return shape, cost, rate limits, or freshness of the snapshot. With annotations carrying the behavioral burden, 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?

Two sentences: a front-loaded statement of what the snapshot contains, followed by a one-line framing of its role. No filler or repetition. The dense metric list is efficient, though several entries ("toll", "gardener", "funnel") are opaque enough to cost some clarity.

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?

For a zero-parameter read-only tool with no output schema, the description does the work of describing what comes back (the metric families), which is the main thing an agent needs. It is not exhaustive about each metric's meaning, but nothing required to invoke the tool 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?

The tool takes zero parameters (empty object schema, required: []), so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies the tool is called with no arguments.

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 conveys that this returns a snapshot of mesh-wide metrics and enumerates the metric families (held/thin/isolated counts, links, catalog size, treasury, bounties, federation, funnel, gardener). However, it uses the noun phrase "A snapshot of the mesh" with no verb and leans heavily on domain jargon, so an agent can't be fully certain what the tool does. It never distinguishes itself from plausible siblings such as survey, thin, or programs.

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 baseline to measure work against" implies the tool is a read-first orientation call to run before doing work, which is useful implied usage. But there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., survey or thin) that would tell an agent when this is preferred over a sibling.

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