prepare_memory_refresh

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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact the annotations do not convey: it performs no model call and no memory write. Beyond that it does not disclose what is returned, whether it has side effects on caches, or how long the 'prepared' state remains valid.

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 short sentences with no filler, and the purpose is stated before the constraint. It is efficient, though the extreme terseness borders on cryptic rather than informative.

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 is responsible for explaining what the 'prepared evidence' and 'delta contract' actually contain and how the agent consumes them, and it does not. For a tool the agent must act on rather than merely call, the essential return-shape and downstream-usage information is missing.

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 single parameter memory_id has 0% schema description coverage, so the description carries the full burden of explaining it — yet it says nothing about the parameter at all (format, whether it can be a slug, name, or ID from another memory tool). It does not compensate for the documentation gap.

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 verb 'prepare' and resource 'memory refresh' are present, and the description at least signals scope by negating side effects ('No model call or memory write'). However, the core output terms 'exact current evidence' and 'stable document delta contract' are proprietary jargon that never resolve into a concrete, verifiable artifact, so an agent cannot confidently tell what this produces or how it differs from the similarly named sibling prepare_observations.

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 or when-not-to-use guidance, and no alternative is named despite a crowded sibling set that includes prepare_observations, project_memory_history, and search_project_memory. The only indirect signal is 'No model call or memory write', which merely implies a safe prep step.

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