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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, and the description is consistent with a tool that mutates SSO session state. The description usefully discloses the SSO precondition and the CRD-missing fallback path, but does not explain side effects, permission needs, or the meaning of the readOnly=false hint.

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?

A single compact sentence chain that front-loads the SSO step and the deduction logic. It is dense with semicolons but wastes no words; a minor readability cost rather than bloat.

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 values need no elaboration, and the main resolution path is covered. However, for a 5-parameter tool with 60% schema coverage and a non-read-only annotation, the description leaves the context/tail parameters and the side effects of the SSO step under-specified.

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 60%: profile, context_id and notification are documented in the schema, while tail and context are not. The description ties 'profile' and 'notificación' to the workflow and explains the ~100-line default that maps to the tail parameter, but adds nothing about context, context_id or tail bounds.

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 specific workflow: perform SSO on the given profile, deduce the Argo Application and cluster from the notification, fall back to a label lookup (argocd.argoproj.io/instance=<app>), and return logs. It is clear what the tool produces, though it never explicitly frames the output as a diagnosis and the 'autodiagnóstico' intent is only implied by the name.

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?

Usage is only implied: you have a notification and want to triage it. There is no explicit when-to-use guidance, no mention of alternatives such as argocd_debug, argocd_app_unhealthy or k8s_describe, and no statement of when not to use it.

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