Get stock snapshots

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful behavioral context: output is 'normalized', news is optional, and filters are applied server-side. However, it does not explain what normalization means or what happens when news scraping is enabled.

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, front-loaded sentence. Every phrase carries meaning: normalized, snapshots, optional news, server-side filters. There is no wasted text.

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?

Despite having five parameters, a nested customFilters object, no output schema, and many sibling tools, the description provides only a one-line summary. It does not describe return values, filter behavior, news output, or how this snapshot tool relates to similar market tools.

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%, so the description needs to compensate. It vaguely alludes to 'optional news' and 'server-side filters' but does not map these to scrapeNewsHeadlines, customFilters, exchange, proxy, or the symbols format. This leaves the agent without meaningful parameter semantics.

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 and resource: 'Get normalized symbol snapshots'. It also distinguishes the tool from sibling quote/price tools by mentioning normalized snapshots, optional news, and server-side filters.

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 offers no guidance on when to use this tool versus alternatives like market_get_quotes, market_get_price, or market_screen. It states what the tool does but not the conditions or use cases that call for it.

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