jekyll_token_list

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

With no annotations provided, the description carries the full burden, and it does disclose the key safety trait ('Read-only') plus the categorization behavior of the result. However, it says nothing about whether it scans the project root, whether results are grouped/sorted, or how large a token set it returns, leaving meaningful behavioral gaps for a scan-style tool.

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?

A single front-loaded sentence that names the verb, resource, scope and categories, with 'Read-only' as a short trailing tag. Nothing is padded or repeated.

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, no-output-schema read tool, the description covers purpose, scope and the categories returned, which is close to sufficient. It could still note that it reflects the scanned project and whether an empty result means no tokens were found, but nothing essential is missing.

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 the baseline is 4; there is nothing for the description to disambiguate. The categorization list adds minor interpretive value about result shape rather than parameter meaning.

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 (List) and resource (design tokens discovered in SCSS) and clarifies the two token flavors (CSS custom properties and Sass variables). It is clearly distinguishable from jekyll_scss_list and jekyll_token_get/update, so an agent can select it without opening any schema.

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 description implies when this tool is useful (discovering existing tokens) but never states it explicitly, nor does it name alternatives or exclusions relative to jekyll_token_get or jekyll_scss_list. Usage must be inferred from the purpose statement.

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