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

Annotations only cover the safety profile (readOnly, non-destructive, closed world); the description goes well beyond that by disclosing the concrete data source identifier (crafting-network/event-demand@1), a freshness guarantee ('recomputed at most once a day'), snapshot semantics, determinism/'never depends on the caller', and the fact that only counts and dates are returned. It even documents inclusion/exclusion rules (craft-fair is never a tag, untagged events are dropped) that an agent could not infer from structured fields.

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 long but information-dense: the first sentence states the resource, then scope, then accounting rules, then field semantics, then constraints — a sensible front-to-back order with essentially no filler. The only redundancy is the opening sentence largely restating the title, which costs it the top mark.

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?

With no output schema and no parameters, the description carries the full burden of describing the result, and it does so completely: it enumerates every returned field (label, count, online, earliest, regions) and defines each one. No further detail would be needed to interpret 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?

The tool takes zero parameters, so the baseline of 4 applies. The description usefully makes the no-argument nature meaningful by explaining that the answer is caller-independent and precomputed, rather than leaving the empty schema unexplained.

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?

States a specific verb+resource combination ('Upcoming event counts by network craft') and then substantiates it with exact scope (next 60 days, Pacific, per network craft tag from the manifest). An agent can tell what data comes back without opening any schema. It does not, however, distinguish itself from the closely-named sibling count_events_by_craft, leaving a real ambiguity unresolved.

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 explicit when-to-use guidance, and no attempt to route the agent between this tool and the near-identical siblings count_events_by_craft and count_events_by_state. The only usage-adjacent information is the negative constraint that the answer never depends on the caller, which describes determinism rather than selection criteria.

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