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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so no side effects are expected. The description adds useful behavioral context beyond annotations: the tool reads an agent-private profile rather than general data, and it enumerates the categories of state it surfaces, which helps the agent know what to expect.

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?

The description is two sentences with no filler. The first sentence front-loads the result content, and the second sentence gives a clear usage directive. Every phrase earns its place.

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-parameter, read-only tool with no output schema, the description covers what is returned, when to call it, and why it matters. It could be more explicit about the exact output shape, but the listed categories are sufficient for an agent to know whether this tool is relevant.

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 has zero parameters and schema description coverage is 100%, so there is nothing for the description to explain about parameters. The baseline of 4 applies, and the description adds relevant context about what the profile contains rather than parameter details.

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 clearly states a specific verb ('Read') and resource ('YOUR agent profile'), and enumerates exactly what the tool returns: remembered preferences, recent searches, recent per-entity actions, and top entities. It also distinguishes itself from general search/retrieval siblings by emphasizing that this reads the agent's own stored profile.

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 description explicitly says when to call it ('at task start') and why ('to reuse what past sessions learned'), including a concrete example about dietary defaults. It does not explicitly name when not to use it or name an alternative tool like remember, but the timing and purpose are clear enough to guide an agent.

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