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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: results are sorted by importance and the result count is hard-capped at 30, a constraint absent from the schema. It does not explain what 'importance' is based on or what happens when a project has no memories.

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 tight sentences with the purpose and content scope front-loaded and the parameter constraint trailing. Nothing is redundant or padded.

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 simple two-parameter read tool with full annotations and no output schema, this covers nearly everything an agent needs. The remaining gap is the format expected for the required `project` argument, which is the one thing that could cause a failed call.

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 coverage is 0%, so the description carries the burden. It usefully adds the undocumented max of 30 for `limit` and implies `project` selects a single project's memories, but never says whether `project` is an ID, slug, or display name, nor what the default limit is (only the schema's default=15 conveys that).

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 ('Returns the most important saved memories for one project') plus the content categories and ordering. It does not explicitly distinguish itself from siblings like memory_list or memory_search, but the project-scoped, importance-ranked framing is clear enough to select on.

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: reach for this when you want a ranked, project-scoped digest rather than a raw listing or search. No explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative, so the agent must infer the boundary.

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