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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so safety is partly covered. The description adds meaningful behavior beyond them: the two permission levels and exactly what each grants ('read' = read-only, 'write' = read + write + delete), which is critical since write implicitly enables deletion. It does not address revocation or repeat-call behavior, leaving a minor gap.

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 dense, front-loaded sentences with no wasted prose; the permission semantics come right after the core action. The leading '[stores]' tag is unexplained noise that slightly detracts from an otherwise tight description.

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 mutation tool with no output schema but with annotations, the description covers the action, prerequisites, and permission semantics adequately. Missing only secondary details such as revocation, error cases, or the consequence of sharing a namespace repeatedly.

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 60%, so the description should compensate, and it does for the key parameter by explaining the permission enum values semantically ('read' vs 'write' including delete). It also references the handle+secret requirement. It does not clarify 'grantee' or 'namespace' beyond the schema, so it is not fully compensating.

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 states a specific verb ('Share') and resource ('a memory namespace') plus the target ('another handle'). This is unambiguous and distinguishable from sibling memory tools like store_memory, search_memory, or memory_retain, which operate on content rather than namespace permissions.

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?

It gives a clear precondition — 'Owner only — registered handle + secret required' — which tells the agent when the call is valid. It stops short of naming alternatives or exclusions (e.g., what to do for non-owned namespaces), so it is clear context without full routing guidance.

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