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

Although annotations already declare readOnly/idempotent/non-destructive, the description adds real context: connection-scoped permission, no settings change, no memory-storage consumption, no cross-user access, and fail-closed error behavior. It stops short of describing latency or what 'unavailable' concretely looks like, so it is strong but not exhaustive.

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?

Purpose and the empty-object requirement are front-loaded, and every clause adds a distinct constraint. It is dense with some redundancy — the 'never permit automatic saving' condition is stated twice in close succession — but nothing is filler.

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 carries the return contract and does so precisely (automaticSavingAllowed, mode, consentVersion) while explicitly excluding expected-but-absent data. For a pre-flight permission check, nothing an agent needs in order to call it safely is missing.

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?

A zero-parameter tool, but the description does more than restate the empty schema: it mandates sending only an empty object and explicitly forbids smuggling conversation content, user IDs or consent claims into the call — a guardrail the schema cannot express.

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 and resource — 'Read the current automatic-memory permission for this authenticated STEM connection' — and immediately scopes the result ('not saved memories or account-wide settings'), which separates it from recall/remember siblings that touch actual memory content.

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 explicit timing ('before any automatic context save') and an explicit decision rule: only 'automaticSavingAllowed exactly true' permits a best-effort save, while false, unavailable or errors never do. It also names the boundary against alternatives — host confirmations and user no-save instructions are not overridden.

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