List Things

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

With no annotations provided, the description itself must convey behavior. It says 'List all things', clearly indicating a read-only operation with no side effects, which is sufficient for a simple list tool. However, it does not mention any details like pagination, ordering, or output format, but those are likely in the documented output schema. It adds some transparency but not much beyond the obvious.

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 a single, clear sentence with no redundancy. It states exactly what the tool does with no wasted words.

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 listing tool, the description is complete. It clearly states the purpose ('List all things') and adds a parenthetical clarification ('trackable values'), which fully explains the scope. With no annotations and no parameters, nothing more is needed.

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)Skip, so there is nothing to explain. The schema coverage is 100% (none), and the description directly matches the tool's behavior. No ambiguity.

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 exactly what the tool does: 'List all things (trackable values).' It uses a specific verb ('list') with a clear resource ('things') and clarifies the scope ('all') and nature ('trackable values'), distinguishing it from sibling tools like 'get_thing' or 'list_chores'.

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 the use case (listing all things) but does not explicitly state when to choose this over alternatives. Sibling tools like get_thing or list_chores are not mentioned, though the distinct resource type makes it obvious. It provides clear context but no explicit exclusions or alternatives.

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