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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so 'Read-only' is pure repetition of structured data and earns no credit. The remaining value is the sketch of returned content (key memories, related items, other names), but nothing is said about behavior when the entity is not found or when the name is ambiguous.

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?

One tight sentence with the entity types up front and the matching rule and read-only note trailing. Only the redundant 'Read-only' clause fails to earn its place against the annotations.

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 must carry return-value meaning, and it does gesture at the profile contents, which is adequate cover. However it omits miss/ambiguity behavior and any hint of the profile's structure or size, leaving meaningful gaps for a lookup tool.

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?

Single parameter with 100% schema description coverage, so the baseline is 3. The description's 'match by name or key' duplicates the schema's own 'canonical key or name' wording, adding no matching rules, case sensitivity, or precedence between name and key.

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 names a specific verb and resource (show what is saved about a named entity) and enumerates the entity kinds it covers (person, company, product, project, tool, topic) plus the profile contents (key memories, related items, other names). It is clearly a single-entity profile lookup rather than a bulk search, but it never explicitly contrasts itself with siblings like search or recall_memories.

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?

Only 'Match by name or key' is offered, which is invocation syntax rather than usage guidance. There is no statement of when to prefer this over search, recall_memories, or fetch, and no exclusions or prerequisites.

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