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

readOnlyHint=true already covers the safety profile, so the description's added value is the guarantee that values are never returned (a real security-relevant behavior) plus disclosure of the truncation/total/returned/scope envelope. It does not mention rate limits or permission requirements, so it isn't exhaustive.

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 tight sentences with zero filler. The return shape is front-loaded where an agent deciding whether to call this will read it first, and the scope rule follows as the operative constraint.

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 absorbs the burden of describing return values, and it does so concretely (row fields plus total/returned/truncated/scope). Combined with a fully documented input schema and read-only annotation, an agent has everything needed to call this correctly.

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 the schema itself documents namespace, all_namespaces, name, and the scope_required error far more precisely than the description. The description only restates the conjunction rule at a high level, so baseline 3 is appropriate — it adds little beyond structured fields.

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 (Fetch) and resource (ConfigMap summary rows) and enumerates exactly which fields come back: name, namespace, data key names, count, age. The explicit '(never the values)' clause separates it from secret-reading siblings like get_secrets without the agent needing to open another schema.

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?

Gives a clear selection condition for the list mode: 'A list needs namespace or all_namespaces=true'. It doesn't name an explicit alternative tool to use instead when the agent wants data values, so it stops short of full when-not guidance, but the operating context is unambiguous.

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