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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds the store-vs-national scoping behavior, but says nothing about freshness, caching, or rate limits. With an output schema present, a 3 is appropriate.

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 front-loaded sentence with the scoping rule stated immediately and zero filler. Nothing to trim.

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-optional-parameter read tool with a full schema, annotations, and an output schema, the description covers the essential modes. Minor weakness: it says 'national list' where the schema says 'vertical-wide list', a small terminological mismatch that could mildly confuse on the restaurant/global verticals.

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% and the store_id/vertical descriptions are richer than the tool description (including the restaurant-vertical caveat and the vertical enum values). The description's 'national list when no store is given' largely restates schema text, so it adds little beyond the baseline.

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 verb+resource — '7NOW trending search terms' — and clarifies the scope varies by store. It is distinguishable from sibling tools like sevennow_suggest and sevennow_search, but it never names or contrasts with an alternative, so it falls short of 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?

It implies the two usage modes (with a store_id for regional results, without for the national list), which is useful context. However, it gives no explicit when-to-use/when-not guidance and names no alternative sibling tool, leaving selection largely to inference.

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