list_templates

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

Annotations already provide readOnlyHint and openWorldHint, so safety and world-scope are covered. The description adds the scope 'all stored... of the CamelMailer server,' which is useful, but it does not disclose output format, ordering, or pagination behavior. It does not contradict the annotations.

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 one short, front-loaded sentence with no filler. Every word earns its place and the key action and resource are immediately clear.

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 list operation with read-only and open-world annotations, the description is largely complete. The only minor gap is the lack of detail about the return value shape, but this is not critical for correct invocation of a parameterless listing 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 tool has zero parameters, and the input schema is essentially empty. The baseline for zero-parameter tools is 4, and the description does not need to add parameter-level details. It correctly describes the operation without inventing parameter semantics.

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 clearly states a specific verb and resource: 'List all stored message templates of the CamelMailer server.' It is unambiguous and distinguishes templates from sibling resources like layouts or emails, although it does not explicitly name an alternative 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 usage is implied rather than explicitly stated: an agent would use this tool when it needs to enumerate available message templates. There are no explicit when-to-use/when-not-to-use instructions or references to alternatives, but the purpose is simple enough that the context is fairly obvious.

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