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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals the pagination order (alphabetical), the effect of `tickers` (ignores pagination params), and that search/min_market_cap order results by market_cap desc. It does not mention rate limits or response shape, but it covers the most consequential behaviors.

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, each densely packed with distinct information. It front-loads the core purpose, then adds the universe composition, pagination mode, and filter list without repetition or fluff. Every sentence earns its place; it is appropriately sized for a tool with 10 parameters.

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 complexity (10 params, no output schema, no annotations), the description provides a solid overview of universe scope, special parameters, and filtering behavior. It does not describe the return payload shape, but for a list operation with a cursor, the response format is typically inferable. The description is complete enough for an agent to select and invoke the tool correctly for most use cases.

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 100%, so the baseline is 3. The description adds meaningful context beyond schema: what 'active' means, the universe composition (US equities plus R: and X: symbols), and the alphabetically-with-cursor pagination behavior. It also reinforces the `tickers` parameter's bulk-row behavior, which is only partially implied in the schema.

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 opens with a specific verb+resource: 'List active tickers from the Tickerbot universe', immediately clarifying the tool's function. It distinguishes itself from siblings by describing the universe scope and the unique `tickers` bulk-lookup mode, setting it apart from single-ticker tools like `tickerbot_get_ticker` and scan tools.

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?

It provides clear usage context: when to use the `tickers` parameter for bulk lookup versus walking the universe with `cursor` pagination. It also lists supported filters, which helps the agent decide when to call this tool. However, it does not explicitly contrast with alternatives like `tickerbot_scan` or `tickerbot_search_news`, leaving some ambiguity for edge cases.

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