store_list

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

With no annotations, the description carries the full transparency burden. It discloses read-only status, lack of pagination, ordering (oldest first), live-record filter, and scope confinement. It does not mention error handling or rate limits, but for a simple list operation this is strong coverage.

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?

Three tightly packed sentences with zero wasted words. The main action is front-loaded, followed by behavioral constraints and alternatives. Every sentence adds value.

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?

Covers purpose, ordering, metadata fields, lack of pagination, alternatives, read-only nature, and scope. With no output schema, it does not describe the full record shape, but the mention of 'each with _id/_created/_updated metadata' gives a reasonable picture. Adequate for selecting and invoking the tool.

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 0%, so the description must clarify parameters. It explains that 'collection' refers to a SOIL collection and points to store_collections for valid names, but 'app_id' is only implied by 'store_scope' and not directly described. Partial compensation for the missing schema descriptions.

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 clearly states the tool returns every live record in a specified SOIL collection, ordered oldest first, including metadata. It distinguishes itself from siblings by explicitly noting it is unfiltered and unpaginated, and by naming store_search and store_collections as alternatives.

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?

Provides explicit when-to-use guidance: 'prefer store_search once a collection grows large' and 'store_collections to discover collection names.' Also notes read-only behavior and confinement to store_scope, which helps agents decide between this and other store tools.

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