List JSM alert notes

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

Annotations already indicate read-only, idempotent, non-destructive behavior, and the description adds meaningful context beyond that: default ordering, opaque cursor pagination rather than numeric offsets, the distinction between human notes and integration updates, and response format behavior. This is rich, accurate behavioral disclosure.

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 well structured with clear sections: overview, usage rationale, arguments, return shape, examples, and a pagination caveat. Every sentence contributes practical information, and the most decision-relevant detail (what this tool returns and when to use it) is front-loaded.

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?

Given the output schema and rich annotations, the description is fully adequate for an agent to select and invoke the tool correctly. It covers ordering, pagination, the full alert id requirement, response formats, and example usage. Nothing an agent needs for correct invocation 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?

Input schema coverage is 100%, so the baseline is 3. The description adds value by emphasizing that alert_id is the full id and not tinyId, explaining the opaque cursor semantics again, and giving example parameter combinations for natural-language use cases. This goes beyond merely restating schema field descriptions.

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 a specific verb ('List'), a specific resource ('notes on a JSM alert's activity timeline'), and the default ordering ('newest first'). It clearly identifies these as human comments, distinguishing them from related alert actions and from the sibling log tool.

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 gives actionable guidance: 'Read them before acting on an alert so you don't repeat work someone already did.' It also provides example queries showing when to use different limits and orderings. It does not explicitly compare to siblings like jsm_list_alert_logs, but the context is clear enough.

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