context

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

No annotations are provided, so the description carries the full behavioral burden. 'Read' implies non-mutation, but the description says nothing about cost, size, whether the snapshot is cached or live, or whether 'unresolved operations' reflects pending writes — all relevant for a context tool.

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 terse sentence with no filler, and the enumeration is front-loaded. It is arguably over-compressed for the ambiguity it needs to resolve, but nothing in it is wasted.

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?

An output schema exists, so return values need not be explained. Still, with no annotations and a generic name shared with a sibling 'read' tool, the definition leaves the agent without the when/why context needed to choose it confidently.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a parameterless snapshot by not referencing any inputs.

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 does name what the tool returns (application, target, capabilities, shared editing workflow, unresolved operations), which is more than a tautology of the bare name 'context'. However, it is a noun list with only the verb 'Read' rather than a stated resource and scope, so an agent cannot easily tell how it differs from the sibling 'read' or 'operations' 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?

There is no statement of when to call this versus the sibling 'read' or 'operations' tools, and no prerequisites or exclusions. The agent must infer that this is an initial session-context fetch, which is a guess rather than guidance.

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