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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds genuinely new behavioral detail: authentication is via Authorization or X-API-Key header, and the tool performs no inference or actions. It stops short of describing response shape or whether the home is empty on first read.

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?

Three short sentences, front-loaded with purpose, then auth mechanism, then scope boundary. No filler or repetition of the tool name.

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 zero-param read with no output schema, the main remaining unknown is what the memory home returns (structure, size, pagination, behavior when empty) and the description says nothing about it. Auth and safety needs are covered, so it is adequate but incomplete.

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?

Zero-parameter tool, so the baseline is 4. The description earns its place by explicitly stating the owner key goes in a header rather than an argument, preempting an agent's attempt to pass a key in the empty schema.

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 a specific resource (private memory home), and the qualifier 'private' plus 'storage only; no inference or actions' distinguishes it from siblings like home_public, home_export, and home_remember. An agent can tell what it retrieves without opening the schema.

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?

Usage is implied by 'read your private memory home' and the privacy qualifier hints at the contrast with home_public, but no alternative is named and no when/when-not condition is given. The agent must infer that home_export is for exporting and home_post for writing.

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