propose_memory

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

Discloses that memories are proposed for human review, not immediately stored, and warns against storing sensitive data. Could mention the review process, but transparent enough given no annotations.

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 sentences efficiently convey purpose, usage, and constraints. No wasted words; every sentence adds value.

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?

Despite clear purpose, the description omits return values, post-proposal workflow, and parameter details. For a tool with 13 parameters and no output schema, more completeness is needed.

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?

With 0% schema description coverage and 13 parameters, the description provides no parameter-specific details. The general guidance does not compensate for the lack of parameter explanations.

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 tool's purpose: 'Propose a repo memory for later human review.' It specifies when to use it (end of non-trivial tasks with durable lessons) and distinguishes from siblings by emphasizing proposal vs. direct storage.

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?

Explicitly provides when to use (non-trivial tasks, specific lesson types) and when not (secrets, trivial churn). Also gives preference for 1-3 high-signal proposals, offering clear guidance.

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