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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description goes well beyond them: it explains that the apply seals values into every deployment and rolls the workloads, that deleting the last key causes removal of the sealed Secret, and that a reconcile would otherwise reinstate deleted values. It also distinguishes a refusal from an error and notes that an empty catalogue is not a refusal.

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?

Front-loaded with the core action, then the consequences of applying and not applying. It is information-dense but somewhat long, and the heavy use of all-caps emphasis (CLEARED, REMOVES, NOT) is a little noisy, though every sentence carries substance.

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?

For a one-parameter, no-output-schema mutation tool with annotations covering the safety profile, the description supplies everything an agent needs: the effect on running workloads, the deletion behavior, and the refusal conditions. Success-response detail is not required since no output schema exists.

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 100% for the single application_id parameter, so the baseline is 3. The description adds meaningful semantics by stating 'Takes no values - the ones applied are the ones already stored', which clarifies that no secret payload is supplied here, giving a small lift above the schema 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+resource: 'Seal an Application's stored environment secrets into every deployment of it and roll the workloads that read them.' It explicitly separates itself from the sibling 'set' operation by explaining that setting a value does not touch what is running until it is applied, so an agent can tell it apart from set_application_env_secret/delete_application_env_secret without opening a schema.

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?

Gives explicit when-to-use (the step that makes a stored value reach a running Application), covers the inverse case (a CLEARED last key also applies, removing the sealed Secret), and enumerates the precise conditions under which it refuses (not deployed yet, tearing down, unsealable deployment, no Kubernetes Secret Ankra can derive). Nothing is left to inference.

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