reference_get_tickers

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention that results may be paginated via the limit parameter, that 'all' may be constrained by a default limit of 1000, or what the response format looks like. It simply states the query intent without addressing these operational details.

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 a single, direct sentence that immediately states the tool's purpose. It contains no filler words and is well-structured for quick parsing.

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?

With nine optional parameters, no output schema, and no annotations, the description is too minimal to give the agent a complete picture. It omits filter capabilities, pagination behavior, and the fact that the default limit may not return all tickers in one call, making it under-specified for this tool's complexity.

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%, and the description does not explain any of the nine parameters (sort, limit, order, active, market, search, symbol, exchange, symbol_type). The agent must infer their semantics from the names alone, with no additional guidance.

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 uses a specific verb 'Query' and clearly identifies the resource: 'all ticker symbols supported by Polygon (stocks, crypto, forex).' This distinguishes it from sibling tools like reference_get_ticker_details or reference_get_ticker_types, which focus on specific attributes rather than the full list.

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 implies the tool is for retrieving the full set of tickers, but it does not explicitly state when to use this over alternatives such as reference_get_ticker_details or reference_get_ticker_types, nor does it mention any exclusions or prerequisites.

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