k8s_get_secret_detail

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

Without annotations, the description carries full weight and discloses key behavioral traits: default hides values, decode shows actual decoded values, and decoded secrets may contain sensitive credentials. It does not cover error handling or output format details, but the caution about sensitivity adds significant value.

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?

The description is three sentences with no filler. The first sentence states the core purpose, the second explains the default behavior and an option, and the third adds a necessary caution. Every sentence earns its place.

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?

Given no output schema, the description gives a rough idea of return values (key names or decoded values) but omits details like the JSON structure, base64 encoding status, and error behavior. For a tool dealing with sensitive data, these gaps reduce completeness.

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 description explicitly explains the 'decode' parameter's effect ('Set decode=True to include the actual decoded values'), which is the only non-obvious parameter. However, required parameters like 'name', 'context', and 'namespace' are left to self-explanatory naming, with 0% schema description coverage.

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 clearly states the verb 'Get' and resource 'a Kubernetes Secret', and distinguishes from sibling tools like k8s_list_secret by specifying that it retrieves a single secret's details. The additional detail about default key-name-only behavior and the decode option further clarifies the specific functionality.

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 description provides a security caution and hints at when to use the decode parameter ('with caution'), but it does not explicitly contrast this tool with alternatives like k8s_get_resource or list_secret. There is no direct 'when to use vs when not to use' guidance, leaving some ambiguity for the agent.

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