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

Annotations already cover read-only safety, yet the description adds material context: returns [] when the scope has no memory, requires a paid plan and a credential not scoped to a project, and marks cross-project results with foreign=true. These are exactly the operational traits an agent cannot infer from structured fields.

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 edge case are front-loaded, and each sentence adds a distinct fact. However, it is one dense ~120-word paragraph with no structural breaks, which makes the per-parameter guidance harder to scan than it needs to be.

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?

Covers all five parameters, defaults, auth prerequisites, the empty-result case, and the foreign=true marker for a tool with no output schema. The only gap is the shape of an individual returned memory item, which the agent must discover empirically.

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?

With 0% schema description coverage, the description carries the full burden and does: scope (= repo folder name), limit (1–100, default 25), git_remote (URL from git remote get-url origin, with alias-resolution behavior), crossProject (fills from other projects, foreign=true), workspaceId (default vs. explicit). Minor note: the documented limit range 1–100 is tighter than the schema's unbounded integer.

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 — loads the most recent memories for a scope — and explicitly contrasts with a query-based sibling via 'sin query'. An agent can immediately tell this apart from mem_search or mem_get without opening either 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?

Gives clear context for use: 'al empezar a trabajar en un repo' and 'si vas a trabajar issues de otro workspace, cárgalo también con su workspaceId'. The 'sin query' framing implicitly routes query-based lookups elsewhere, but no alternative tool is ever named explicitly.

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