athena_rehydration_handoff_delta

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

No annotations are given, so the description carries the burden. It discloses the fresh-sync operation and that the delta is read-only and content-addressed, but omits side effects of the sync, permission needs, or return structure.

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, front-loaded with purpose, no wasted words. The distinction from successor task routing is efficiently stated.

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?

Despite a clear purpose, the tool has 3 undocumented parameters, no output schema, and no annotations. The description lacks details on alternatives like athena_rehydration_handoff_resume and what the delta contains, leaving an agent under-prepared for invocation.

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 description provides no explanation for the three parameters (remote, loop_id, shared_remote_mode). An agent cannot know how to set these parameters correctly.

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?

Clear verb 'derive' with resource 'read-only, content-addressed handoff delta describing what a successor agent must rehydrate.' Explicitly states it is distinct from successor task routing, helping disambiguate from sibling tools.

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?

Mentions the process (fresh-sync then derive) and provides an exclusion by saying 'Distinct from successor task routing.' However, it does not name alternative tools like athena_rehydration_handoff_resume or detail when to use this over them, leaving some ambiguity.

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