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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses that the tool is admin-only, returns already-generated images, and connects to a worker poll concept. It also signals a follow-up workflow with marketing_graphics, which is valuable behavioral context not present in annotations.

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 tightly packed: purpose, access restriction, filter usage, sibling-tool transition, and reusable output hints all fit into a few lines. The Args block is clearly formatted and the most important operational guidance is front-loaded.

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 an output schema present and safety annotations in place, the description covers all operational essentials: admin access, filter semantics, limit bounds, and the relationship to marketing_graphics. No critical calling information is missing; the only minor gap is the lack of an explicit allowlist of content_type values, which is likely dynamic and out of scope for a static description.

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%, but the description fully compensates by explaining each parameter: since is an ISO timestamptz, ticker filters current items for a symbol, type is an allowlisted content_type or research_drop, and limit is constrained to 1–200 with a default of 50. This adds meaning far beyond the bare schema properties.

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 identifies the tool as returning the latest teasers and already-generated images, and explicitly contrasts it with marketing_graphics for live formats. It lacks a direct imperative verb like 'List' or 'Get', but the scope and resource are unmistakable.

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?

Provides explicit routing guidance: use ticker for symbol-scoped items, type for cross-symbol content_type filtering, and since for the worker poll. It also tells the agent when to call marketing_graphics and when to reuse items[].images[], leaving no ambiguity about selection.

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