k8s_expose_resource

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

No annotations are provided, so the description carries full burden. It states it 'creates a Service', implying a write operation, but does not disclose potential side effects (e.g., conflicting with existing Services, permission requirements, or resource existence checks). This is insufficient transparency for a mutation tool.

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 concise at two sentences, but given the tool's complexity (11 parameters), it is under-specified. It could include more parameter guidance without being overly verbose. The structure is adequate but could be improved.

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 0% schema coverage, no annotations, no output schema, and 11 parameters, the description is severely incomplete. It fails to explain critical parameters (e.g., 'context', 'namespace', 'selector') and does not specify return values or error scenarios. The agent lacks essential information to use the tool 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?

The input schema has 11 parameters with 0% description coverage. The description only mentions 'type' and implies the target resource (deployment/pod), but it does not explain any other parameters such as 'labels', 'target_port', 'protocol', or 'selector'. The AI cannot infer proper usage for most parameters.

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 tool's purpose: 'Expose a deployment or pod as a new Kubernetes Service.' It specifies the action (expose) and the resources involved (deployment/pod -> Service). There are no sibling tools with 'expose' in the name, so it is distinct.

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 like k8s_create_resource or k8s_apply_resource for creating Services. It only mentions the 'type' parameter values but lacks explicit 'when to use' or 'when not to use' instructions.

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