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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the payload is a static catalogue of types/versions plus their purpose, which is useful context, but says nothing about ordering, size, or whether the catalogue can change.

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?

One tightly packed sentence with no filler, and the scoping qualifier ('the Test Bench checks') is placed early. Nothing could be removed without losing meaning.

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 no-argument, read-only, output-schema-less tool, the description carries the main burden and it does describe the shape of the returned items (type, version, purpose). The notable residual gap is the tension between the name 'list_messages' and a catalogue of message types, which could cause a mis-call.

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 nothing for the description to disambiguate. Baseline 4 applies; the description's only relevant contribution is confirming the returned set is scoped to 'what the Test Bench checks'.

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 resource: the ISO 20022 message types and versions the Test Bench checks, along with their purpose. That is clear enough to know what you get back. It does not, however, differentiate from sibling list_* tools (list_samples, list_data_endpoints, list_corporate_actions), and the name 'list_messages' could mislead toward listing individual messages rather than the supported type catalogue.

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?

There is no statement of when to call this versus alternatives, no prerequisite, and no exclusion. An agent might infer it should consult this before validate_message, but that inference is not supported by any text in the description.

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