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

The readOnlyHint annotation already declares the safety profile, and the description's 'Read-only' merely restates it. It does add useful content by naming the observable state (clusters, namespaces, chart versions, deployment states), but says nothing about pagination, scoping, or what happens for an undeployed application.

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?

Two short sentences, front-loaded with the core purpose and with zero filler. The trailing 'Read-only' is slightly redundant given the readOnlyHint annotation, but overall the text is tight.

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 no output schema, the description usefully enumerates the returned fields (clusters, namespaces, chart versions, deployment states), which is what an agent needs to judge relevance. Only the absence of any usage context keeps it from being fully 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?

Schema description coverage is 100%, so the single application_id parameter is already fully documented in the schema. The description adds no format, ID-source, or lookup detail beyond that baseline.

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?

States a specific verb ('Get') and resource ('where an Application is deployed') and enumerates the returned facets (clusters, namespaces, chart versions, deployment states). It does not explicitly differentiate itself from nearby siblings like get_stack_deployments or get_application, but the purpose is 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?

There is no guidance on when to prefer this tool over get_application, get_deployments, or list_application_installations, and no stated prerequisites or exclusions. Usage is only implied by the resource named.

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