hyperfeed

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

With no annotations, the description carries full burden. It discloses 'newest first' ordering, 'No login required', and the default behavior of omitting stream to get all three. While it doesn't mention output format or pagination, it gives meaningful behavioral context beyond a bare statement.

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?

Two sentences, front-loaded with the core purpose, followed by precise usage details and an alternative pointer. Every sentence serves a purpose with no 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 simple 2-parameter tool with no output schema, the description covers purpose, usable values, ordering, and alternative. It omits any hint of the return shape, which would be useful, but the tool's simplicity and the description's clarity make it sufficient for most invocation decisions.

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 0%, so the description compensates by fully explaining the `stream` parameter with its enum-like values and default. The `limit` parameter is left to the schema, but its name and default are self-explanatory. Overall, the description adds significant meaning to the most ambiguous parameter.

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 opens with 'Browse HyperFeed', a specific verb and resource, and immediately clarifies the content: 'curated stream of agentic-AI news, agent releases/updates, and SF events.' It distinguishes from sibling hyperfeed_digest by explicitly pointing to it for personalized briefs, making the tool's unique role clear.

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?

Usage is well-guided: 'stream ∈ {news, releases, events} (omit for all three)' and 'For a user's personalized morning brief use hyperfeed_digest instead' provide explicit when-to-use and an alternative. 'No login required' sets context for when authentication is unnecessary.

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