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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still contributes real value by disclosing what is deliberately withheld: destination addresses, delivery records, and raw alert state are excluded, and channel names represent configuration rather than live delivery targets — an agent would otherwise wrongly expect those fields.

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 tight sentences, zero filler, with the core action front-loaded and the exclusion clause immediately following. Every phrase carries information an agent could not get from the structured fields.

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 needn't be explained, and the description neatly covers scope and deliberate omissions. Gaps remain around the identifier's provenance and error/not-found behavior for a single-resource lookup tool.

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?

There is one parameter (ruleId) with 0% schema description coverage, so the description must carry the semantics and it does not. It never says that ruleId identifies the alert, whether it comes from list_alerts, or what happens for an unknown id; only the pattern in the schema hints at format.

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 and resource: 'Read one owned alert configuration' plus 'recorded diagnostic applicability'. The word 'one' and 'owned' scope it as a single-record fetch, implicitly distinguishing it from the sibling list_alerts, though it never names that sibling explicitly.

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: 'one owned alert configuration' suggests retrieval by identifier after an alert is already known, and 'owned' hints at an authorization precondition. There is no explicit statement of when to use this versus list_alerts, nor of behavior when the rule does not exist or is not owned.

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