get_pod_logs

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

Beyond the readOnlyHint and destructiveHint annotations, the description adds a non-obvious behavior: falls back to the previous container instance if the current one is crashing. It also explains the empty container default, which adds practical context not captured by the schema.

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 efficient: a one-sentence purpose, a compact Args block, and a single behavioral note. Every line earns its place with no redundancy or fluff.

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 an output schema present, return values are covered elsewhere. The description covers the tool's core behavior, parameters, and the distinctive fallback behavior. It doesn't mention permissions or rate limits, but annotations provide safety context, so the coverage is nearly complete.

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?

With 0% schema description coverage, the description lists all five parameters with brief but useful semantics: cluster is a managed cluster name, container empty picks the default, lines sets the trailing count. This compensates well for the missing schema descriptions, though some parameters (e.g., pod, namespace) only restate their names.

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 uses a specific verb ('Tail') and resource ('logs from a pod on a managed cluster'), clearly distinguishing it from sibling tools like get_resource or query_events. The purpose is immediately clear and unambiguous.

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 implies usage by defining the exact context (cluster, namespace, pod), but does not explicitly name alternatives or exclusions. It provides enough context for an agent to infer when to use it, but lacks explicit 'when to use vs. not' guidance.

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