tv_alert_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds 'Best-effort', suggesting the tool may not always succeed, which is a behavioral trait beyond annotations. No other behavioral details are given.

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 concise at two sentences. However, the first part 'Open the alerts panel' may be an implementation detail that adds little value; it could be more direct. Overall, it is brief and 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?

The description lacks details on what exactly is listed (e.g., alert IDs, messages, timestamps) and the implications of 'best-effort' (e.g., possible failure). With no output schema, the agent has insufficient context about the return value.

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 tool has no parameters, so the description does not need to add parameter semantics. Schema description coverage is 100%, so baseline is 4.

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 'Open the alerts panel and list existing alert messages', which clearly indicates the action (list) and resource (alerts). However, the phrase 'Open the alerts panel' is slightly misleading as the tool name suggests listing only, not opening a panel. It distinguishes from siblings like tv_alert_create and tv_alert_delete.

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?

No usage guidelines are provided. The description does not mention when to use this tool versus alternatives such as tv_alert_create or tv_alert_delete, nor does it specify prerequisites or context.

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