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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds non-redundant context: the required read scope (an auth constraint not exposed in annotations) and the exhaustive set of destination kinds returned, so the agent knows nothing is filtered out.

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?

Three short sentences, each earning its place: scope prerequisite, what is listed (with kinds), and how the result is consumed. The permission constraint is front-loaded and nothing is padded.

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-parameter, read-only list tool with no output schema, the description covers purpose, permission, scope, and downstream use adequately. Only minor gaps remain, such as whether results are paginated or what fields each destination carries, which the absence of an output schema leaves slightly open.

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 takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description correctly implies an unfiltered full listing rather than misrepresenting an absent filtering capability.

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?

States a specific verb and resource ('Lists the project's notification destinations (channels)') and enumerates all covered kinds (webhook, telegram, discord, slack, ntfy, pushover, msteams, googlechat, email). This clearly separates it from the sibling mutators create_destination, update_destination, delete_destination, and test_destination.

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?

Clearly signals the access prerequisite ('Requires the read scope or higher') and states the downstream purpose ('Their ids are what set_route takes'), which is genuine when-to-use context linking it to set_route. It stops short of naming explicit alternatives or exclusions, but an agent knows exactly why and when to call it.

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