k8s_create_secret

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Create' implies a write/mutation operation, it doesn't disclose critical behavioral traits: whether this requires specific RBAC permissions, whether it's idempotent (overwrites existing secrets?), what happens on failure, or any rate limits. For a Kubernetes mutation tool, this leaves significant gaps.

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 a single, efficient sentence with zero waste. It's appropriately sized for a tool with good schema documentation and gets straight to the point without unnecessary elaboration.

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 Kubernetes secret creation tool with no annotations and no output schema, the description is insufficient. It doesn't cover important context: what permissions are needed, whether it validates secret data format, what happens if the secret already exists, what the return value looks like, or error conditions. Given the complexity of Kubernetes operations, this leaves the agent with significant uncertainty.

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 the schema already documents all 4 parameters thoroughly. The description adds minimal value beyond what's in the schema - it mentions 'literal values' which hints at the 'data' parameter being key-value pairs, but this is already clear from the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 action ('Create') and resource ('generic secret from literal values'), providing a specific verb+resource combination. It distinguishes this from other secret-related tools like 'k8s_get_secret' or 'k8s_delete_secret' by focusing on creation, though it doesn't explicitly differentiate from 'k8s_apply_manifest' which could also create secrets.

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 no guidance on when to use this tool versus alternatives. It doesn't mention when to choose this over 'k8s_apply_manifest' for secret creation, nor does it specify prerequisites like required permissions or cluster context. The agent must infer usage from the tool name alone.

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