black_souls_session_log_append

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

Annotations indicate it is read-only false and not idempotent, but the description does not disclose potential side effects like log size limits, ordering guarantees, or whether the append overwrites existing entries. It merely restates the operation.

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?

While the single sentence is concise, it omits essential details. The description is under-specified for a tool with 4 parameters and no schema descriptions, making it inefficient for correct agent usage.

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?

Given the complexity of the game context and the lack of annotation support, the description fails to provide sufficient context. It does not explain the purpose of the session log, how it differs from other storage tools, or when an event is considered 'significant'.

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?

With 0% schema description coverage, the description must explain the parameters. It does not mention 'event_type' enum values, the meaning of 'frame' and 'scene', or constraints on 'summary'. No examples or clarifications are provided.

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 action ('Append') and the target resource ('persistent session log'). It distinguishes the tool from its sibling 'black_souls_session_log_read', which performs the opposite operation. The qualifier 'significant gameplay event' adds specificity to the intended use.

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?

No guidance is provided on when to use this tool versus alternatives such as scratchpad or memory writes. There is no mention of prerequisites, when not to use it, or how it fits into a typical workflow.

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