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

With no annotations, the description carries the full burden and does well: it discloses the 4000-character limit, that storage is platform-wide rather than per-wallet, that the operation is effectively write-only, and that it returns an index id. It omits auth requirements, rate limits, and whether entries are mutable, so not quite complete.

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 tight sentences, front-loaded with the verb and primary resource, then immediately adding the scoping constraints an agent needs. Zero filler.

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 write-only log tool with no annotations and no output schema, the description covers behavior and the return value (index id) reasonably well, but the unexplained duplicate 'c'/'content' parameters leave an agent unable to call it correctly without guessing.

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 coverage is 0% and there are two undocumented string parameters, 'c' and 'content'. The description explains the 4000-character limit implied for content but never clarifies what 'c' is or how the two parameters relate, leaving a significant semantic gap the schema does not fill.

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) and resource (the platform's agent-memory log), plus scope details: the 4000-character cap and the returned index id. An agent instantly understands it is a write-only log append, distinct from anything else in the sibling list.

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?

It implies usage by warning that no endpoint reads the data back and framing the tool as a 'write-only record log,' which tells the agent when the data will (not) be retrievable. But it never states when to choose this over alternatives or what an appropriate use case is, so guidance remains implied rather than explicit.

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