lock_memory

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

The description complements annotations: it confirms mutation (consistent with readOnlyHint=false) and non-destructive (destructiveHint=false). It adds ownership enforcement detail not in annotations. No contradiction.

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 short sentences with no superfluous words. Front-loaded with the core purpose.

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 tool with no output schema, the description covers the essential purpose and a key condition. It lacks details on return values or error cases, but the tool's simplicity may not require it.

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?

Input schema covers both parameters with descriptions (100% coverage). The description adds value by clarifying the role of agent_id in ownership enforcement, which is not in the schema.

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 clearly states the action (lock), resource (memory), effect (prevent deletion and editing), and a key condition (ownership enforcement). It distinguishes from sibling tools like 'unlock_memory' and 'delete_memory'.

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?

The description implies when to use (to prevent deletion/editing) and mentions ownership enforcement, but does not explicitly state when not to use or compare to alternatives beyond the sibling list context.

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