k8s__get_network_policies

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

No annotations provided, description only states it lists policies with certain fields. Does not disclose read-only nature, authorization needs, or whether it returns all policies or filtered by namespace. Lacks important behavioral context for a mutation-ambiguous 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?

Single sentence, no fluff. Front-loaded with action and resource.

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, but description provides some info on returned content. For a simple tool with one optional parameter, this is mostly adequate, though could explicitly state it returns a list of policy objects.

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 covers 100% of parameter meaning (namespace with default). Description adds value by indicating the output includes podSelector, ingress/egress rules, which is not in the schema.

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?

Description uses specific verb 'List' and resource 'network policies', and mentions included items (podSelector, ingress/egress rules). Clearly distinguishes from sibling tools focused on pods, logs, deployments, etc.

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 on when to use this tool vs alternatives like k8s__describe_resource. No mention of prerequisites or exclusions.

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