work_context

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read operation and rules out filesystem reconstruction, but says nothing about permissions, scope, identity binding semantics, or what 'volatile' context means for callers; an output schema exists so return values need not be described, but the operational profile is thin.

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?

A single front-loaded sentence with the verb first and no filler; every clause is doing something. The phrasing is dense to the point of obscurity, but it is not padded.

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 annotations, a single undocumented parameter, and many closely named context-reading siblings, the description is not sufficient for reliable selection or invocation. The output schema covers return values, but the gaps around routing and parameter meaning remain.

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?

There is one parameter, work_ref, with 0% schema description coverage, so the description must compensate and largely does not. 'Identity-bound' loosely hints that work_ref is an identity reference, but its expected format, source, and relationship to work identity are never stated.

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 has a specific verb ('Read') and a stated resource ('identity-bound canonical/progressive/volatile context'), but the resource is opaque jargon that an agent cannot map to a concrete artifact. 'Without filesystem reconstruction' gestures at a boundary, but the core purpose remains only partially intelligible.

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 versus alternatives such as read_context, recovery_context, or audit_context, all of which sit adjacent in the sibling list. The only hint is the negative clause 'without filesystem reconstruction', which implies an alternative without naming it or the condition that selects this tool.

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