service_list

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

Description starts with '[READ]' signaling read-only operation. No annotations, so description carries burden. Does not disclose pagination, ordering, or auth requirements, but basic behavior is clear.

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?

Extremely concise: two-line description and two-line parameter list. No redundant text. Every sentence adds value.

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?

Simple list operation with optional filter. Description covers input, output fields, and read-only property. Lacks output format details, but adequate for a basic list tool.

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 coverage is 0%, so description must compensate. Explains namespace behavior and target purpose. Adds meaning beyond schema (type/name only). Could specify target validation, but sufficient.

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 clearly states 'List services' with specific attributes (name, namespace, type, cluster IP, ports). Distinguishes from sibling list tools (e.g., pod_list, deployment_list).

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?

Specifies namespace usage ('omit for all namespaces') and target parameter. Lacks explicit when-to-use vs alternatives, but context is clear from sibling tool names.

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