agtmem_append

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

There are no annotations, so the description carries the full disclosure burden. It adds one useful behavioral guarantee, 'Safe under concurrency,' but does not explain mutation side effects, behavior when the note does not exist, or how dates are generated. The statement is not contradictory, but it is thin on operational detail.

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 one tight sentence with no filler; every part adds signal: operation, target, dated-section behavior, and concurrency safety. It is front-loaded and efficient, though short.

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?

For a simple two-parameter append tool, the description gives the core operation and a relevant safety property, but is missing explicit parameter meaning, behavior for nonexistent notes, and return value expectations. There is enough to guess the intended use but not enough to cover all likely agent questions.

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?

Schema description coverage is 0%, and the description must therefore compensate for missing parameter documentation. The operation implies 'id' identifies the existing note and 'text' is the content of the appended section, but the description never explicitly explains either parameter or any formatting/constraint requirements. This is minimal compensation.

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 states a specific verb ('Append'), a specific resource ('an existing note'), and a distinguishing behavior ('dated section'), which clearly separates it from siblings like agtmem_write, agtmem_read, or agtmem_search. Even without naming alternatives, the operation and target are unambiguous.

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 the tool is for adding a dated section to an existing note rather than creating or replacing one, but it does not explicitly say when to prefer this over agtmem_write or mention any exclusions. An agent can infer the intended use case but is not given direct routing guidance.

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