Show alert

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

Annotations already declare this as readOnly, idempotent, openWorld, and non-destructive. The description adds the GET endpoint but no further behavioral context such as auth requirements, error handling, or return format. With strong annotations, this level of added detail is adequate 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?

The description is concise with three short sentences. The opening 'Show alert' is somewhat redundant with the title, but the rest is efficient and front-loaded with the core action. It earns near-perfect marks for scale.

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 simple single-ID retrieval tool with no output schema and comprehensive annotations, the description and schema provide sufficient context. It states what it does and the endpoint, and the parameter is fully documented. Minor gap: no explicit return value description, but 'retrieves details' implies the response.

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 100% coverage: the only parameter (id) is clearly described as 'The ID of the alert to retrieve.' The description adds no new parameter-level meaning beyond the schema, so the baseline of 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 'Retrieves the details of an existing alert,' which is a specific verb+resource combination. It clearly distinguishes showAlert from sibling listAlerts by focusing on retrieving a single alert by ID, and the API endpoint reinforces this purpose.

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 clear context: use this tool when you need details of a specific existing alert. It does not explicitly mention alternatives like listAlerts, but the context is unambiguous enough for an agent to infer appropriate usage.

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