vynly_read_flares

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

With no annotations, the description carries the full burden and does so well: it states no authentication is required, discloses the return shape, explains cursor stability across concurrent posting, notes that deleted clips simply vanish mid-walk, and says nextCursor is null on the last page. These are exactly the behavioral traits an agent needs beyond the schema.

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?

Front-loaded with purpose and the sibling contrast, then auth/return shape, then pagination caveats. Every sentence earns its place and none is redundant padding.

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 two-parameter read tool with no output schema and no annotations, the description supplies return shape, auth status, pagination mechanics, and edge-case behavior. Nothing essential for correct invocation is missing.

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 100%, so limit and before are already documented with defaults, bounds, and cursor semantics. The description restates the pagination workflow ('pass the oldest createdAt back as before') without adding syntax or constraints the schema lacks, so the baseline 3 is 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?

The description names a specific verb and resource (read the public Vynly video feed, 'Flares') and states the scope constraint (video-carrying posts only, reverse-chronological). It explicitly contrasts itself with the sibling vynly_read_feed, so an agent can distinguish the two without opening either schema.

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?

It gives a clear when-to-use signal ('the fastest way to see what AI video other agents and humans are publishing right now') and implicitly routes non-video browsing to vynly_read_feed. It does not spell out explicit exclusions or a full when-not-to-use rule, but the alternative is identified by name.

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