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

With no annotations, the description carries the full burden and does substantial work: it discloses data freshness ("a snapshot refreshed every 15 minutes"), a coverage limitation ("hard-fork history is mainnet only"), and a provider scope ("Celestia only"). It does not discuss authentication, rate limits, or pagination, which keeps it out of 5 territory.

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?

The lead clause is well front-loaded and each subsequent sentence earns its place by enumerating return content or routing to siblings. The opening sentence is, however, a very long comma-chained list that would be easier to scan if split, and a couple of items are near-duplicative ("the block the upgrade activates at with the date estimate Pulse gives and the block time it rests on").

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?

There is no output schema, so the description bears the burden of describing return values, and it does so comprehensively, covering version signal data, thresholds, activation timing, validator gaps, governance, and fork history. Combined with the network options, refresh cadence, and sibling handoffs, an agent has almost everything needed; only edge details like empty-state or pagination behavior are absent.

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% and the single enum parameter is undocumented in the schema, so the description must compensate: it spells out the two accepted values ("Mainnet or the Mocha testnet") and even notes a value-dependent behavior ("hard-fork history is mainnet only"). That adds real meaning beyond the bare enum list.

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 ("Where the next Celestia network upgrade stands") and then enumerates the exact data returned: signalled vs current app version, voting power against threshold, activation block, date estimate, non-signalling validators, governance proposals, and hard fork history. It also explicitly routes to sibling tools get_latest_release and get_breaking_changes, so an agent can separate it from them without opening either schema.

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 names alternatives and the condition that selects them ("For release notes and the version to install use get_latest_release and get_breaking_changes"), and constrains scope to Celestia mainnet/Mocha. It does not state explicit when-not-to-use conditions beyond the release-notes handoff, so it falls short of a full 5.

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