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 usefully adds that the result set mixes valid and deliberately broken samples, each carrying an issue code, which tells the agent what to expect in the payload. It says nothing about ordering, pagination, or the size of the library.

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?

Two short sentences with no filler; the content of the library is front-loaded and the sibling routing follows immediately. Nothing could be removed without losing information.

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 simple read-only list tool with no output schema and a fully documented parameter, the description covers what the tool returns and how to get the underlying XML. Only the absence of any note on result size or ordering keeps it from being fully complete.

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?

Schema description coverage is 100% and the single optional parameter is a fully enumerated message-type filter documented in the schema itself. The description adds no further semantics about the filter, so the baseline of 3 applies — the schema does all the work here.

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 identifies the resource concretely — the Test Bench sample library — and specifies its contents: one valid message per type plus broken samples annotated with their issue codes. It also distinguishes itself from get_sample, which returns the XML. The only gap is that the listing verb itself is implied rather than stated.

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 sentence 'Use get_sample for the XML' explicitly routes the agent to the correct sibling when the actual message payload is needed, which is the main ambiguity for a samples tool. It stops short of stating when to prefer list_samples outright (e.g., to discover which samples or issue codes exist), but the contrast is clear enough to act on.

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