Append a log line (RoxyBot)

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

With no annotations, the description must carry the full behavioral burden. It discloses that data is written to log.jsonl on this Mac only and that the return value is {ack: true}, but it does not cover failure modes, permissions, concurrency, or idempotency.

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 two tightly written sentences, front-loads the main action, and packs parameter and return details without unnecessary repetition.

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 append-log tool with no annotations or output schema, the description covers the core action, local storage location, and return shape. However, missing semantics for doel and status, plus absent failure-mode details, leave meaningful gaps for correct invocation.

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%, so the description must compensate. It names all five parameters and adds useful detail for type (call, sms, whatsapp, …), ts (epoch ms), and optional inhoud, but leaves doel and status unexplained.

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 and resource: record one call or message line from the RoxyBot phone. It clearly identifies the tool as a logging operation, though it does not explicitly distinguish it from any sibling tool.

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 that this is used to log a call or message line, but gives no explicit guidance on when to use it versus alternatives or when not to use it. No sibling tool is referenced as an alternative.

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