pin_memory

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

Since no annotations accompany the tool, the description carries the full responsibility of explaining behavior. It only says 'Pin a memory to core status' and does not specify what 'core status' implies, whether the operation is reversible, what side effects might occur, or any permission-related constraints. The description effectively relies on the tool name itself.

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?

The description is highly concise, with a single sentence and no filler. However, this conciseness is achieved by omitting nearly all the information an agent would need; it earns its place as a short purpose statement but does not go beyond that, making the brevity a trade-off against completeness.

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 no annotations, no output schema, and a bare schema with a single undocumented parameter, the description leaves central concepts undefined. An agent cannot infer what 'core status' means, how the memory is located via 'node_id', or what the tool actually does beyond the name. The description is not complete enough to support correct invocation.

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?

The input schema has only one parameter, 'node_id', but its description coverage is 0%. The description does nothing to explain what 'node_id' represents, how to obtain it, or how it relates to the 'memory' being pinned. This is a critical gap because neither the schema nor the description supplies this required meaning.

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 clear verb ('Pin'), a specific resource ('a memory'), and the intended outcome ('core status'), and it also implicitly distinguishes the tool from its sibling 'unpin_memory' by describing the opposite action. An agent can confidently connect the tool to its core function without consulting other tools.

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 provides no guidance on when to use 'pin_memory' versus related tools such as 'memory_store', 'memory_amend', or 'unpin_memory'. It does not mention prerequisites, use cases, or exclusion conditions, so the agent receives no direction about when this tool is the right choice.

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