black_souls_scratchpad_write

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

Annotations provide minimal info (all false). The description says 'Update' but does not clarify whether writes overwrite or merge, nor the behavior of optional parameters. No mention of persistence or side effects.

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?

A single sentence of 10 words conveys the core purpose without extraneous text. It is front-loaded and efficient.

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 tool has 3 optional parameters (one nested) and many sibling tools, the description lacks context on interaction with scratchpad_read, session scope, and overwrite behavior. An output schema exists but is not available to compensate.

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%. While the description maps 'notes' and 'flags' to the respective parameters, it does not explain their semantics (e.g., flags are boolean keys). The 'append_action' parameter is only partially described as 'recent actions' with no details on frame, action, result.

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 updates the session scratchpad, listing specific fields (notes, flags, recent actions). It distinguishes from siblings like scratchpad_read (read) and memory_write (different resource).

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 on when to use this tool versus alternatives (e.g., scratchpad_read for reading, memory_write for memory). The description does not mention exclusions or context.

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