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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the trailing 'Read-only' is largely redundant with that. However, the description adds genuinely valuable interpretive context beyond the structured fields: entries are tagged as measured vs. told, a 'told' item remains a claim regardless of age, and an empty range means 'nothing recorded' rather than 'all well'. This meaning-level disclosure is exactly what annotations cannot carry.

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?

Five short sentences, front-loaded with what the tool assembles before qualifying how to read the results. Every sentence adds a distinct piece of meaning (sources, provenance tagging, empty-state semantics, safety). Slightly dense but no filler.

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 input or output schema, the description carries the full burden of conveying contents, and it does so reasonably well by enumerating the joined record types and the measured/told provenance model. It does not describe ordering guarantees, volume, or time-range behavior, but for a parameterless read-only aggregation it is close to complete.

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 schema baseline is 4 and there is nothing for the description to clarify. No contradiction or omitted param meaning exists.

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 the resource (a chronological diary of the project assembled from existing Boosthis records) and enumerates the source material it joins: fixes served, claims checked, promises and verdicts, history moves, and changes assistants filed. This distinguishes it from siblings like boosthis_promises or boosthis_ai_changes, which cover only a single source. The verb is somewhat lyrical ('life in order') rather than crisp, but an agent can tell what it returns.

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 statement of when to call this vs. the single-source siblings (boosthis_promises, boosthis_alerts, boosthis_trend). The only guidance is interpretive ('an empty stretch means nothing was recorded'), which is useful but not about tool selection. An agent must infer that this is the consolidated timeline view.

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