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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: it is a point-in-time snapshot ('Live totals at this moment') and it 'Reads published files only,' disclosing the data source and that no mutation or private state is touched. It does not mention pagination or size limits, but for a zero-arg status read that is minor.

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 description is short and front-loads the payload ('Live totals at this moment: ...') before the exclusions. The standalone sentence 'No parameters' is slightly redundant with an empty input schema, and the negation list is dense, but overall it is tight and every clause carries routing or content information.

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, the description carries the burden of describing return values and it does so by enumerating the six content areas, including a pointer to the longest verifiable silence. For a simple zero-param read this is sufficient; only the exact shape/format of the returned fields is left unspecified, which is a small 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 and the description confirms 'No parameters,' so there is no parameter semantics to explain. Baseline for a parameterless tool is 4, and nothing here misrepresents the empty input schema.

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 names a concrete resource (live TACET totals) and enumerates the exact payload an agent gets back: epochs closed, epochs anchored in Bitcoin, models on the map, snapshot counts, signed silence proofs, and a pointer to the longest verifiable silence. It also differentiates itself from three siblings by negation (not a weekly Silence Report, not one model's record, not a proof bundle), so an agent can route correctly without opening the 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?

Explicit exclusions are given: 'This is not a weekly Silence Report, not one model's record, and not a proof bundle,' which effectively steers the agent away from silence_report, lookup_model, and get_silence_proof. It does not name those alternatives as tool IDs, so the routing is implied rather than spelled out, but the when-not guidance is clear.

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