baron_memory_append

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

With no annotations provided, the description carries full burden. It only says 'durable' but omits key behavioral traits: side effects, permissions, success/error behavior, idempotency, or storage limits. This is insufficient for a mutation tool with 4 parameters and no output schema.

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 front-load the core purpose and then detail operations efficiently. No extraneous words. The colon-based structure is somewhat dense but still clear. Very minor improvement possible by separating operation specs more clearly.

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?

Given the tool's complexity (4 params, enum, no output schema, no annotations), the description covers purpose and operation variants but lacks return value hints, error conditions, prerequisites, and parameter constraints (e.g., tag format, body length). The title-required contradiction further reduces completeness.

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 description adds meaning to the 'op' enum by explaining field requirements per operation (e.g., 'learning' requires title+body, 'followup' requires title with optional body/tags). However, it contradicts the schema by implying 'title' is always required while the schema marks only 'op' as required. Other parameters (body, tags) get no additional semantics beyond 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 this tool records data durably in Baron's own store, distinguishing it from siblings like baron_memory_query (querying) and baron_issue_write (issue tracking). It also details two specific operations ('learning' and 'followup') with field requirements, making the purpose highly specific.

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 usage context by specifying 'not a provider's store' and briefly defining each operation, but does not explicitly guide when to choose this tool over siblings (e.g., baron_memory_query for retrieval) or when not to use it. No exclusions or alternatives are named.

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