tickerbot_list_system_universes

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

With no annotations provided, the description carries the full behavioral burden. It discloses that the universes are built-in, rebalanced monthly, and based on 30-day trailing dollar volume, plus availability to all accounts. This provides useful context beyond mere listing, though it doesn't specify response format or potential limitations, which is acceptable for a simple read operation.

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 two sentences, front-loaded with the core action, and every clause adds value: what is listed, examples, definition, availability, and usage. There is no wasted wording or repetition.

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 parameterless list tool with no output schema, the description is adequately complete. It explains what the universes are, why they exist, and how to use the resulting slugs. It doesn't describe the exact response shape, but for a simple list operation the expectation is straightforward.

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, so the baseline is 4. The description correctly notes the slugs but doesn't need to add parameter details since none exist. The schema already confirms an empty object, so the description provides sufficient context for how to use the returned slugs.

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 'List the built-in system universes' with specific slugs and their definition, distinguishing it from sibling tools like tickerbot_list_universes which likely handles all universes. The verb and resource are explicit and unambiguous.

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 when to use this tool: to get system universe slugs that can be used in scans/signals or subscriptions. It notes availability to all accounts, implying it is the go-to for built-in universes. It doesn't explicitly mention alternatives like list_universes for custom universes, but the context is clear.

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