Re-read the export

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavior beyond that: it always targets the *newest* export rather than a caller-chosen one, and it is a legitimate recovery path after a load failure. It stops short of saying what happens when no export exists or whether in-memory state is replaced.

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?

Two sentences, zero filler, with the core action ('re-read the newest export') front-loaded before the situational guidance. Every clause earns its place.

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 zero-param, fully annotated, no-output-schema tool, the description covers what it does and when to invoke it. The remaining gap — failure modes such as 'no export present' or whether it replaces a currently loaded snapshot — is minor but would be useful for a recovery-oriented tool.

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 is 4 and the schema has nothing for the description to disambiguate. The description correctly implies selection is implicit (newest export) rather than parameterized, which is consistent with the empty 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?

States a specific verb+resource: 'Re-read the newest export from disk,' which tells the agent exactly what data is loaded and from where. It is clearly distinct from the read/search siblings (read_library_text, search_cases, get_source_text) because it refreshes an already-loaded export rather than querying new content, though it never names an alternative explicitly.

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?

Gives two concrete triggers: after the user exports a fresh backup, and as a retry after a load failure. That is clear when-to-use coverage; only explicit when-not guidance is absent, which is low-impact for a zero-parameter refresh tool with no overlapping siblings.

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