memory_propose

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

No annotations are provided, and the description contains zero behavioral information. The tool could be a read, write, or mutation operation; the description gives no clue about side effects, permissions, or return behavior.

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?

Though the description is minimal (one word), this is under-specification rather than efficient conciseness. It omits all substantive information and does not front-load any useful details.

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 description is completely inadequate for a tool with no annotations and no output schema. It leaves the agent without any understanding of what this tool does, its side effects, or its relationship to siblings.

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?

While the tool has no parameters, the description adds no meaning about the operation's inputs or effect. Even with a high schema coverage baseline, the tautological description fails to convey what the 'propose' action entails.

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 is identical to the tool name ("memory propose") and provides no verb or resource clarification. It fails to indicate any specific action or object, making it a pure tautology with no purpose clarity.

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?

No guidance is given on when to use this tool versus alternatives like memory_search or memory_promote. The absence of any contextual or conditional information leaves the agent without direction.

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