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

No annotations are supplied, so the description carries the full behavioral burden, and it says almost nothing beyond the verb. It does not disclose persistence semantics, whether a write can overwrite or duplicate an existing memory, what happens on a conflict, or the authentication requirement — the only auth hint lives in a deprecated parameter's schema note about the bearer token. The one real signal, "shared team memory," implies writes are visible to other agents, which is useful but far from sufficient for an 8-parameter mutation.

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?

It is a single front-loaded sentence with zero padding, so nothing is wasted. But that terseness comes at the cost of substance — the shortness reflects under-specification rather than discipline.

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 8 parameters, 6 of them required, no annotations, and no output schema, the description should be doing far more work. It says nothing about what a successful write returns (an id? a resolved memory?), how required fields are validated, or what the memory lifecycle looks like after writing — leaving an agent to guess on nearly every call decision.

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 description coverage is only 13%, so the description must compensate, and it does not. "Typed" and "attributed" loosely gesture at the type and author_agent fields, but the six required parameters — project, session, subject, content, author_agent, type — get no explanation of format, allowed type values, or scoping rules. derived_from is entirely unexplained, leaving nothing to indicate how provenance should be recorded.

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 gives a specific verb plus resource ("Write ... memory") and adds meaningful qualifiers: typed, attributed, and shared team scope. An agent knows immediately this is a write operation against team memory, unlike the read-oriented siblings memory_get / memory_search. It stops short of naming a sibling or the conditions that would route an agent here instead.

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?

There is no when-to-use guidance: nothing says whether to write a new memory vs. memory_resolve or memory_retract an existing one, nor when a memory should be recorded at all. The words "shared team" hint at the collaborative context but give no operational rule for selecting this tool over its siblings.

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