get_application_logs

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It's a read-only log retrieval tool, which is fairly benign and low-risk, but the description doesn't disclose tail-line limits (max 1000), pagination behavior, or what happens if pods/containers are not found. For a non-destructive read tool, this is acceptable but not rich.

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?

Description is brief and front-loaded with the core purpose in the first line. The elaboration sentence about use cases adds value without bloat. Could be slightly more compact but is efficient overall.

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?

An output schema exists, so return format need not be explained. The description covers the tool's purpose and when it's useful. Annotations are missing but the tool is a low-risk read operation; the key gap is the lack of guidance on distinguishing from sibling read tools and clarifying pod/container selection behavior. Adequate for a read-only log 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 description coverage is 0%, so the description must compensate. However, the schema itself has rich per-parameter descriptions (Application name, ArgoCD instance name, specific pod name, container name, tail lines, since seconds). The description adds no parameter-level semantics beyond what the schema already provides. With well-documented schema params, baseline 3 is appropriate.

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 states a clear purpose: 'Get pod logs for an application' with a specific verb+resource. It elaborates on use cases (debugging, checking startup errors, monitoring runtime). It doesn't explicitly distinguish from siblings, but the siblings list shows many read tools for app state/status/diff/history, while this one is uniquely about logs, so ambiguity is low.

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 gives implied usage ('useful for debugging application issues, checking startup errors, or monitoring runtime behavior') but no explicit when-not or alternative guidance. Among many sibling tools, it doesn't clarify when to use logs vs get_application_status or diagnose_sync_failure. The what-it's-for hint provides moderate direction but with no exclusions.

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