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

The readOnlyHint annotation covers the safety profile, and the description's 'right now' plus content examples provide a little context about the returned information. No additional behavioral traits are disclosed—no pagination, rate limits, or default ordering—so it stays at the minimum viable level rather than earning higher credit.

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?

A single compact sentence front-loads the core purpose and provides concrete examples without any filler or repetition of the title.

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 read-only tool with two optional parameters this is close to adequate, but with no output schema the description could reasonably state what a call returns (e.g., a list of activity items) or what the defaults are for env/limit. The lack of sibling differentiation also leaves an agent unsure whether this or events is the right endpoint.

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 0%, so the description needed to compensate by explaining env and limit, but it mentions neither. The parameter names and constraints in the schema are relatively self-explanatory, but the description adds no meaning about live/test environment selection or how limit controls the result count.

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 the tool as a platform-wide activity feed, naming concrete content types (new listings, completed jobs, bounties) and the 'right now' scope. It doesn't explicitly use a verb or contrast with sibling tools like events, so it doesn't fully earn a 5.

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?

No guidance is given about when to choose this over alternatives; sibling tools such as events, list_jobs, and search_listings overlap with the feed's content, but the description never mentions them or specifies exclusions such as 'use events for ...' or 'use list_jobs for filtered job activity.' The temporal 'right now' hints at broad current activity, but that is implicit rather than stated guidance.

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