List All Quotes

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

With no annotations, the description carries the full burden. It unambiguously presents the operation as a non-mutating retrieval of all stored quotes, which is the key behavioral trait. It does not mention ordering or pagination, but for a zero-parameter list operation the description is sufficiently transparent about the operation's nature.

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, direct sentence with no redundant wording. It opens with the operation and immediately defines the scope. Every word contributes to the meaning.

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?

Given the zero-parameter surface, the description is nearly complete: an agent can safely invoke the tool without additional setup. It does not mention return shape or pagination, but for a simple list-all operation with no output schema, this is acceptable and low-risk.

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 no parameters, and the input schema is empty, so there is no parameter burden on the description. The description's mention of 'every quote' clarifies the retrieval scope, which adds slight semantic value beyond the schema, though not much is required.

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 operation: 'List every quote currently stored in the collection.' The verb is explicit, the resource is specific, and the scope ('every quote') distinguishes it from filtered or random retrieval tools like search_quotes and random_quote.

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 phrase 'every quote currently stored in the collection' gives clear context for when an agent should use this tool: when it needs the full collection. It does not explicitly compare against sibling tools or state when-not-to-use, but the scope is obvious enough to guide selection.

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