prometheus_tsdb_status

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

readOnlyHint=true already establishes this is a safe read, so the '[READ]' prefix is largely redundant. The description does add value by naming the returned content (cardinality stats and top metrics by series count), which is useful since no output schema exists, but it omits cost, cardinality-explosion risk, or default-target behavior details.

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 short lines with the resource/return summary front-loaded and the parameter note after. The 'Args:' boilerplate is slightly mechanical but there is no wasted prose.

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 single-optional-parameter read tool with annotations covering safety, the description is adequate: it says what is read and how to pick a target. It stops short of explaining the scale of the output (how many top metrics, ordering) or when this status view is preferable to related tools, which leaves moderate gaps given there is no output schema.

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 coverage is 0%, so the description must carry the parameter, and it does: 'target: Prometheus target name from config; omit for the default.' This explains both the meaning of the value and the semantics of omitting it, matching the schema's null default.

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 resource (TSDB head cardinality) and a specific output (top metrics by series count), which is more concrete than generic status tools like prometheus_config_status. However, it does not explicitly name how it differs from close siblings such as series_metadata or label_values.

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?

There is no when-to-use guidance, no mention of prerequisites, and no routing to an alternative tool. The '[READ]' tag and the target note only describe the call, not the situation in which this tool is the right choice over series_metadata or observability_overview.

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