engagement_log

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

With no annotations, the description carries the full burden. It usefully discloses that the log is 'append-only,' but it does not explain permissions, idempotency, error behavior, or what the tool returns after appending an entry.

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 definition is a single, front-loaded sentence that avoids filler. The parenthetical field list is dense but informative and does not obscure the core action.

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 an 11-parameter write tool with no annotations, no output schema, and no per-field schema descriptions, the description is too thin. It covers purpose and a rough field inventory but leaves behavioral details and parameter distinctions undocumented.

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. The parenthetical list maps many parameters to meaning (e.g., ts as timestamp, comment_text as full comment text, stop_or_warning as stop state), but it leaves gaps such as the distinction between target_url and target_account, and does not explain value formats or requiredness.

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 ('engagement action to the append-only log') and scopes it to 'executed or owner-completed' actions. It is distinguishable from read-oriented siblings like engagement_report and receipt_list, though it does not explicitly name those alternatives.

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 phrase 'executed or owner-completed engagement action' implies the tool should be used after an action has been carried out, not for planning or review. However, there are no explicit when-to-use/when-not instructions and no named alternatives for comparison.

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