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

With no annotations, the description carries the full burden, and it does disclose ordering ('newest first') and per-item payload ('each item with its date and source'), plus the topical scope boundary. It omits anything about result volume or truncation behavior, which matters for a feed-style tool with a default limit of 50.

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?

It is front-loaded with the core question and the scope disclaimer sits at the end where it does the most boundary-setting work. The middle enumeration is long but each listed category adds real coverage, so the density is justified rather than padded.

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, no-output-schema aggregator the description covers what kinds of things come back and in what order, which is the main risk area. Its gap is behavioral: nothing about the limit parameter, the 90-day ceiling, or what happens when more changes exist than fit in a response.

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 must compensate. It gives meaning to the time window ('last N days'), but says nothing about the undocumented 'limit' parameter, its default of 50, or the 1–90 day cap enforced by the schema, leaving the agent to infer truncation behavior.

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 a specific verb+resource ('What changed on NEAR in the last N days'), then enumerates the concrete change types covered (archived repos, deprecated packages, protocol upgrades, House of Stake proposals, incidents, forum threads, radar alerts). The closing contrast 'NEAR activity only, not general crypto news' sharpens the boundary against non-sibling sources.

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?

The scope statement implies this is a broad recent-activity aggregator, which implicitly distinguishes it from narrow lookups like get_incident or list_proposals. However, it never explicitly says when to reach for this instead of siblings such as list_incidents, list_proposals, or get_breaking_changes, nor when not to use it.

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