Samples List

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses what happens when a sample set is missing (an error naming what to fetch) and that sketch falls back to a stand-in, but it does not state that this is a read-only operation or clarify side effects and permissions.

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 compact at two sentences and front-loads the resource being described. The first sentence is somewhat convoluted because of the parenthetical examples, but there is no wasted sentence.

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 parameterless list tool with an output schema, the description covers the core information and the missing-set behavior. However, it omits the read-only safety expectation and does not connect the tool to samples_fetch or other relevant siblings, leaving a completeness gap for an agent choosing among many tools.

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, so there is no parameter semantics to explain; the baseline for a parameterless tool is 4. The description does not need to compensate for any schema gaps 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 clearly: sample sets used by some built-in voices, and it states the information returned (installed status, size, licence). It does not name a specific verb like 'list', and it does not distinguish this tool from siblings such as samples_fetch or voices_list, so it stops short of a 5.

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 explicit guidance on when to call this tool, when not to call it, or which sibling to use instead. The mention that missing sets raise an error and that sketch uses a stand-in is behavioral context, not usage routing.

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