memory_alias

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds the useful consequence that lookups under either name resolve to the same node, but it never explains the destructive aspect the annotation flags (e.g. whether an alias already bound elsewhere is silently overwritten) or persistence behavior.

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 sentences, zero filler, with the core action and its rationale front-loaded and the return value disclosed last. Nothing is wasted.

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?

An output schema exists, so the return-value note is a bonus rather than a necessity, and the two parameters are fully documented in the schema. The only gap is conflict/overwrite semantics, which the destructiveHint annotation raises but the description does not address.

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 100%, so the baseline is 3, but the description's ``pg`` → ``postgres`` example adds real meaning by clarifying the direction of the alias/canonical relationship that the terse schema descriptions ("The alternative name", "The canonical entity to bind onto") leave slightly ambiguous.

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 concrete verb ("Bind") and resource ("an alternative name to an entity") and reinforces it with a concrete example (``pg`` → ``postgres``). It is clearly distinguishable from most siblings, though it never names the adjacent tools (memory_set_add, memory_graph_relate) that also create bindings.

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 only implied through the example and the phrase "so facts and graph lookups under either name land on the same node." There is no explicit statement of when to prefer aliasing over other binding tools, nor any prerequisite or exclusion guidance.

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