tickerbot_list_universes

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

No annotations are provided, so the description carries the burden. It adds useful behavioral context: each row carries a 'system: true|false' flag, and it implies a read-only listing operation. It does not disclose pagination behavior or auth requirements, but for a list tool these are less critical.

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?

Two sentences, front-loaded with the core purpose, and every clause carries useful information. No filler or redundancy.

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 tool's simplicity (3 optional params, no output schema), the description is nearly complete: it explains purpose, filtering options, and a key output field. It doesn't explain pagination, but that is covered by the schema's 'cursor' and 'limit' descriptions. Overall, sufficient for an agent to use the tool correctly.

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 coverage is 100%, so the baseline is 3. The description adds value by explaining the semantics of the 'owner' parameter (defaults, meaning of 'me/system/all') and drawing an analogy to the signals catalog's 'kind'. This goes beyond the schema descriptions, justifying a 4.

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's function: 'List universes — your saved ones and/or the built-in system universes (top_10, top_100).' It uses a specific verb ('List') and resource ('universes'), and explicitly defines the scope, distinguishing it from sibling list_system_universes by covering both owner and system universes.

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 explains how to filter using the 'owner' parameter ('me', 'system', 'all') and notes the default. However, it does not mention alternatives like tickerbot_list_system_universes, nor when to prefer one over the other. This is a clear omission given the sibling tool exists.

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