get_application_resource_tree

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

No annotations are provided, so the description must carry the burden. It states the output is a 'JSON string with resource tree including nodes and their parent references,' which adds some transparency about the return format. However, it does not disclose edge cases like missing applications, permission requirements, or whether the operation is read-only.

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 concise and well-structured with a purpose line, elaboration, and separate Args/Returns sections. Every sentence is informative, and there is no redundancy or filler.

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 two simple parameters and an output schema exists, the description provides basic context: it returns a JSON string with the resource tree. However, it lacks details on error scenarios, prerequisites, or behavior when resources are absent, making it adequate but not thorough.

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?

The input schema has 0% description coverage, so the description's Arg section is the only source. It provides minimal explanations: 'connection_name: Name of the Argo CD connection' and 'name: Application name,' which essentially restate the parameter names and add little semantic value beyond what the names imply.

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 the tool's purpose: 'Get the Kubernetes resource tree for an application' and elaborates that it shows 'all resources created by the application and their relationships.' This distinguishes it from sibling tools like get_application_managed_resources, which focuses on managed resources without the tree structure.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or scenarios where this tool is preferred over siblings such as get_application or get_application_managed_resources.

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