list_channels

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

With no annotations, the description carries the full burden; "List" implies a safe read, and "configured in your WatchCron project" usefully states the scope of the result set. It does not state pagination behavior, ordering, or what happens when no channels exist, and leaves read-only status implicit rather than declared.

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?

A single front-loaded sentence with zero filler; the resource is named first and the example channel types are a compact parenthetical.

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 zero-param list tool with no output schema, the description conveys enough about return contents (notification channel records of various types) and scope to call it correctly. Minor gaps are the shape of each returned item and pagination, which are low-risk for this tool.

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 schema has zero parameters, which is the baseline-4 case; the description correctly implies a no-argument, project-wide listing. No parameter meaning needs to be added.

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?

Specific verb ("List") plus specific resource ("notification channels") scoped to the WatchCron project, with concrete example types (email, Slack, webhook). It is clearly distinguishable from the monitor-centric siblings (list_monitors, get_monitor, etc.), though it never explicitly contrasts itself with them.

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?

Usage is only implied: an agent can infer this is the discovery call for channels before configuring notifications. There is no explicit when-to-use/when-not-to-use guidance and no mention that it takes no arguments or that it should precede channel selection elsewhere.

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