get_signals

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

With no annotations provided, the description carries full behavioral burden. It discloses the exact cost ($0.03 via x402), the batch limit, the requirement for PRIVATE_KEY, the 402 response without a key, and the guarantee that users are never charged for an error.

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?

Every sentence serves a purpose: cost, contents, usage workflow, payment mechanics, and key requirements. The description is front-loaded with the most critical operational detail (paid nature) and contains no filler.

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?

For a paid feed tool with 3 optional params and no output schema, the description covers all necessary usage context: authentication (PRIVATE_KEY), pricing, error safety, pagination (since), filtering (type), and the integration with get_index. An agent has enough information to invoke correctly.

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?

The schema already describes all three parameters at 100% coverage, so the baseline is 3. The description adds value by explaining the relationship between since and get_index, and by confirming count's maximum of 20. It does not go into deeper detail for each enum value, but the schema already covers that.

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 this as a paid batch endpoint for Polymarket feed items, explicitly listing the three item types (mover, whale_entry, predetermined). It distinguishes itself from free siblings like get_index by noting the paid nature and the requirement to poll get_index first.

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 an explicit workflow: 'Poll get_index (free), then pass since=N for new items; filter with type.' It also clarifies when payment is required, how to obtain price terms without a key, and the compute-first/settle-after behavior.

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