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

With no annotations at all, the description carries the full behavioral burden. It hints at an authorization behavior (elevation token changes the context) but never explains what "data context" vs the elevated context actually return, how the token is supplied, or what happens if it is missing or invalid.

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 no filler; the core operation comes first and the conditional context follows. It is efficient, though the brevity pushes into cryptic territory that the rest of the definition never resolves.

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 tool with no annotations, no output schema, and no parameters, this one sentence is not enough. It omits what the store contains, the meaning of "data context," the return shape, and the origin of the elevation token.

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 schema is empty, which normally sets a baseline of 4, but the description references an input — a "valid elevation token" — that has no corresponding parameter in the schema. That mismatch leaves the agent unsure how, or whether, the token can be passed at invocation.

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 ("Read") and resource ("the shared store"), which cleanly distinguishes it from the sibling store_write. It stops short of naming or contrasting any sibling explicitly, and "shared store" is left undefined, so it lands at clear-but-not-differentiated.

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?

The clause "data context unless a valid elevation token is given" implies a conditional usage mode, so the agent can infer there are two read scopes. However, it never says when to prefer store_read over siblings, nor what qualifies as an elevation token or how to obtain it.

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