memorable_toggle_pin

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. "Toggle" implies a mutation that flips state rather than setting an explicit value, but the description never confirms this, states whether the operation is idempotent, whether it returns the new state, or what happens if the id is invalid — significant gaps for a write tool with zero annotation coverage.

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?

A single well-formed sentence with the action front-loaded and no filler. It is efficient, though its brevity is close to under-specification rather than tightness.

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?

The tool is simple (one required parameter, no output schema, no nested objects), so a short description is defensible. Still, with no annotations and no output schema, the description should at minimum say the call mutates state and whether the resulting pin state is returned.

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?

There is one parameter and schema description coverage is 100%, so the schema already documents that "id" is the unique identifier with a positive-integer constraint. The description adds essentially nothing beyond it, so the baseline of 3 applies.

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?

"Toggle the pinned status of a memory" gives a specific verb and a specific sub-resource, which is far clearer than a generic "update memory" phrasing. It does not differentiate itself from the related sibling memorable_reorder_pinned or explain why one would toggle a pin rather than reorder pinned items, so it stops short of a 5.

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 contains no when-to-use guidance, no mention of prerequisites (memory must exist, must be accessible), and no comparison to alternatives such as memorable_update_memory or memorable_reorder_pinned. The agent must infer usage entirely from the verb.

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