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

With readOnlyHint already covering safety, the description goes well beyond annotations: it enumerates the returned metadata fields, states decoded secret values are never returned, and describes the list envelope (total, returned, truncated, scope). This is exactly the behavioral context an agent needs for a metadata-only read.

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?

Front-loaded with the core purpose and kept dense, with the critical 'no decoded values' caveat placed early. The enumeration of returned fields is long, but since no output schema exists this content is load-bearing rather than padding.

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?

No output schema is present, so the description must carry the return contract, and it does so comprehensively — field list, list envelope, and the explicit exclusion. Nothing material for correct invocation 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 100%, so all four parameters are already documented, and the schema itself restates the namespace/all_namespaces/name relationship. The description adds the list envelope semantics but no new parameter syntax or format detail, so the baseline 3 holds.

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 precise verb+resource ('Fetch Secret metadata') and immediately bounds the scope by enumerating exactly what is returned and, critically, that decoded values never are. This distinguishes it from value-exposing siblings like list_application_env_secrets or set_application_env_secret.

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 scoping requirement for a list (namespace or all_namespaces=true) is given, and a named read is implicitly opposed to a list read, but there is no explicit when-to-use-this-vs-another-tool guidance or named alternative. Usage is implied rather than stated.

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