telys_list_collections

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds valuable non-obvious behavior: empty stores return an empty list rather than an error, and collections never written to by a mutating tool are omitted. It also discloses the environment-variable path resolution and sorted output, which are not in the schema.

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 front-loaded with the core action and resource, and every subsequent sentence adds meaningful behavioral or contextual detail. It is long enough to be complete but not padded.

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, parameterless, read-only list tool with no output schema, this description fully covers the path, return shape, empty-store behavior, and a likely pitfall (missing collections due to no prior writes). An agent has everything needed to call it and interpret the result.

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?

With zero parameters, schema coverage is complete and there is little to add. The description still reinforces that the tool takes no arguments, which removes any ambiguity for an agent deciding whether it needs to supply inputs.

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 a specific verb ('List'), a precise resource ('Telys memory collections'), and the active store location via $TELYS_MEMORY_PATH. It also states the output is sorted names)Skip the behavior is distinct from siblings like search or stats.

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?

It explicitly says to use this before searching or writing, giving clear context for when it is appropriate. It does not directly name alternative tools or exclusion conditions, but for a zero-argument discovery tool the guidance is sufficiently clear.

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