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

With no annotations, the description carries the full burden and does add real behavioral context: a live feed, a hard result cap of 50, and an explicit safety directive that free-text fields are attacker-controlled and must not be executed or rendered as HTML. It stops short of stating pagination or read-only semantics explicitly, but the safety and result-limit disclosures are substantive.

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?

Purpose and endpoint are front-loaded, followed by the cap, then the security note. The security note is long but carries genuine, non-redundant content; nothing here is filler, though it could be tightened.

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 zero-parameter read tool with no output schema, the description covers what it returns (an activity feed), how much (capped at 50), and the key handling caution for the returned free-text fields. What the individual activity records contain is left unspecified, which is a minor gap.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. No parameter meaning is missing.

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 states a specific resource and operation ('Live global activity feed') and even names the underlying endpoint, so the agent knows it is a global aggregate read rather than a per-entity lookup. It does not explicitly contrast itself with siblings like list_agents or market_agents, which keeps it from 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?

There is no indication of when to prefer this global feed over the more specific sibling listings (list_pins, list_agents, market_*), nor any preconditions or exclusions. The only usage-flavored detail is the 50-item cap, which is a constraint rather than guidance.

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