arvan_k8s_get

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds that it outputs JSON by default, but beyond that, no behavioral traits are disclosed. It does not contradict annotations.

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 sentence, making it concise, but it is under-specified. It sacrifices necessary detail for brevity, lacking structured information about parameters or usage.

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 the tool has 6 parameters, no output schema, and numerous sibling tools, the description is inadequate. It does not explain return values, filtering capabilities, or how to use optional parameters, leaving significant gaps for the agent.

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 0%, so the description must compensate. It only elaborates on the 'resource' parameter with an example ('pods'), while ignoring the other five parameters ('name', 'namespace', 'kubeconfig', 'kubeconfig_path', 'output'). The default JSON output is hinted but not explicitly linked to the 'output' parameter.

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 that the tool performs 'kubectl get' operations on Kubernetes resources, with an explicit example of resource='pods'. This makes the purpose clear. However, it does not differentiate from sibling tools like 'arvan_k8s_apply' or 'arvan_kubectl', lacking explicit sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives such as 'arvan_k8s_apply', 'arvan_k8s_delete', or 'arvan_kubectl'. The description only states what the tool does, not the context of use.

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