get_alert_templates

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

Annotations already declare the operation read-only, idempotent, and non-destructive. The description adds meaningful behavioral context beyond that by specifying the return shape (a map), enumerating the possible keys, and explaining the semantic of an empty result. This helps the agent interpret the response correctly.

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 compact and front-loaded: the operation is stated first, followed by the return format and key details, ending with an important edge-case interpretation. Every sentence adds distinct value and there is no redundant filler.

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 read-only tool with one documented parameter and no output schema, the description fully covers what an agent needs: what the tool returns, the allowed keys, and the meaning of an empty result. Nothing critical is missing.

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 only parameter, 'id', is already fully described in the schema as 'Monitor UUID' with 100% coverage. The tool description does not need to repeat this and does not add additional parameter semantics, so the baseline score 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 opens with a specific verb and resource: 'Get all custom alert message templates for a LastPing monitor.' It clearly identifies the product scope and the operation, and the mention of a map keyed by event-type distinguishes it from related mutation tools like set_alert_template.

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 this is the tool to inspect existing custom templates, especially with its note about empty results meaning built-in defaults. However, it never explicitly names the alternative set_alert_template or states when to use one vs. the other, so the guidance is only implied rather than explicit.

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