polymarket-sentiment-shift

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

No annotations provided; description includes cost info and expected result fields but lacks details on data freshness, rate limits, or permissions. Adequate but not rich.

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?

Three sentences, front-loaded with purpose, efficient use of words, no extraneous content.

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?

No output schema, but description explains return fields. Missing mention of data source or update frequency, but overall sufficient for this simple tool.

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 covers all parameters (100% coverage), and description does not add meaningful extra context beyond the schema definitions. Baseline score appropriate.

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?

Clearly states it returns Polymarket prediction markets with biggest recent probability shifts, specifies use cases (elections, crypto, macro), and distinguishes from sibling polymarket tools by focusing on sentiment changes.

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?

Implies usage for detecting consensus changes but does not explicitly state when not to use or compare to alternatives like polymarket-intel or polymarket-accuracy-score.

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