Get tweet-count market metadata

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

With no annotations provided, the description fully discloses behavioral traits: states it is read-only, makes a single HTTPS request to polystrike.xyz, requires no API key, and explains the behavior of deltas during warm-up (null until ready). It also details the sources of the three counters.

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?

Description is concise (single paragraph) and front-loaded with the main verb and resource. Every sentence adds value, covering purpose, usage, return fields, and special conditions without redundant phrasing.

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 no output schema, the description fully explains the return structure (event_id, title, three counters, deltas) and contextualizes deltas as null during warm-up. It also specifies the data source (Polystrike) and the tool's role in the workflow. All relevant aspects are covered.

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 coverage is 100% with a description for the 'account' parameter, including an enum. The description adds context about the tracked accounts (e.g., Elon Musk on X) and explains the return fields, which adds value for understanding output but not for parameter semantics beyond what the schema provides.

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?

Description clearly states it gets live metadata for Polymarket tweet-count markets of a tracked account, listing specific return fields (event_id, title, three counters, deltas). It distinguishes from sibling tools by recommending this as the first call to discover markets before using get_predictions or get_trading_signals.

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?

Explicitly says to call this first to discover active markets and event IDs, mentions free tier and no API key needed, and notes that deltas are null during warm-up. However, it does not explicitly state when not to use it or exclude alternatives beyond the recommendation.

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