Get Alert

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds only the source system and an example call; it says nothing about what an alert record contains or what happens if the ID is unknown (error vs empty), which is the remaining behavioral gap.

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 purpose sentence followed by a short usage block and one example; nothing is redundant. The header/emoji markup and the stray closing </example> tag are minor noise but cost nothing in clarity.

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 read-only getter with 100% schema coverage and declared readOnlyHint, the description plus schema is nearly sufficient. The only missing piece is return-shape information, which has no output schema to carry it.

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% and the single parameter is already documented as "The ID of the alert to retrieve." The example (alertId=3Yr) adds a hint about ID format, but otherwise the description defers entirely to the schema – the baseline case.

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 ("Retrieve a specific alert by ID") and names the source system, Mackerel. The singular "by ID" implicitly contrasts with the sibling list_alerts, but no sibling is named 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?

The "USE THIS TOOL WHEN USERS: Investigate a particular alert" block gives a clear triggering condition, reinforced by a worked example. It does not, however, tell the agent when to prefer list_alerts or get_alert_logs instead.

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