Add entries to a LOG store

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

Annotations indicate readOnlyHint=false (write) and destructiveHint=false (non-destructive), which the description matches by stating 'append' and 'additive.' The description adds behavioral context by specifying that entries are shaped per the store's field schema, going beyond the annotations.

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 that are compact and front-loaded: first sentence describes the core action, second clarifies additive nature and field schema. No wasted words.

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 tool with 2 parameters and no output schema, the description covers purpose, additive behavior, and entry structure. It doesn't explain how to obtain logId or return values, but these are assumed from context. Overall adequate.

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 100% with both parameters described. The description adds context that entries carry optional fields like ts, source, level, message, data and that they conform to the store's field schema, providing semantic value beyond the 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 the tool appends entries to a LOG store, listing the possible fields (ts, source, level, message, data) and calling it additive. It distinguishes from siblings like rootr_query_log_entries (query) and rootr_create_log_store (creation).

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 says 'append one or more entries' and 'additive — existing entries are untouched,' implying use for writing log data. It does not explicitly state when to use versus alternatives like rootr_add_row or rootr_query_log_entries, but the sibling list provides some implicit guidance.

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