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

No annotations are supplied, so the description must carry the full behavioral load. "Live" and "single pull" convey freshness and that it is a non-destructive aggregate read, but there is nothing on auth requirements, whether readings are cached or point-in-time, latency, or behavior when no session is streaming. For a zero-annotation tool this leaves real gaps.

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 lean sentences with the payload list front-loaded and the usage condition second. No filler, no restatement of the title, and every clause carries information.

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 does the necessary work of naming what comes back (proof, human context, writing process, guidance). Given a one-optional-parameter read tool, an agent has enough to call it correctly; only the streaming/no-streaming failure mode is unaddressed.

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 100% and the single session parameter is fully documented in the schema, including the regex, the X-EDNA-Session header fallback, and the "default" behavior. The description adds nothing about the parameter, so the baseline of 3 applies.

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?

Names a specific verb (pull/get) and resource ("live brief") and enumerates the four bundled payloads: current proof, human context, writing process, response guidance. That enumeration maps directly onto the sibling getters (get_human_proof, get_human_context, get_writing_process, get_response_guidance), so the aggregate-vs-single relationship is strongly implied, though never stated outright.

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?

Gives a clear trigger condition: "Call before each answer while an EDNA session is streaming." That tells the agent both when to call and the state the system must be in. It stops short of explicit exclusions, e.g. that the individual component getters exist for non-streaming or targeted lookups.

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