get_alerts_summary

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

With no annotations provided, the description must disclose behavioral traits. It only states the output grouping, but fails to mention that it is a read-only operation, any scope (e.g., all alerts or filtered), or potential limitations. Minimal transparency.

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?

Single sentence that is clear and directly states the tool's functionality without any fluff. Every word earns its place.

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 summary tool with no parameters and an output schema, the description is largely complete. It could mention whether the summary covers all alerts or a specific subset (e.g., time range), but the core purpose is well communicated.

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?

Input schema has zero parameters, so description does not need to add parameter information. Schema description coverage is 100% trivially. The description adds value by specifying grouping details. Baseline 4 for zero-param tool.

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?

Description clearly states the tool returns a summary of alerts grouped by severity and state. The verb 'get' and resource 'summary of alerts' with specific grouping criteria distinguish it from sibling tools that list individual alerts or details.

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 implies use when an aggregate overview is needed, but does not explicitly state when to use this tool versus alternatives like list_alerts or get_alert_details. No 'when not to use' guidance or naming of siblings.

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