clear_computation_journal

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

With no annotations, the description must disclose behavioral traits. It only says 'Clear', which implies a destructive action, but fails to mention any side effects (e.g., whether the journal is immediately erased or if confirmation is needed), reversibility, or impact on ongoing computations. This is insufficient for safe agent 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?

The description is only two words, which is too brief. While conciseness is valued, this lacks essential behavioral information, making it under-specified rather than efficient. The description should front-load critical details about the action's consequences.

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?

The tool is a mutation (clearing a journal) but provides no information about prerequisites (e.g., whether a notebook must be open), return value (despite having an output schema, it is not described), or potential data loss. The description is too minimal to be contextually complete for a destructive operation.

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?

The tool has zero parameters and schema description coverage is 100%. The description does not need to add parameter information, as the schema is already complete and there are no parameters to document. Baseline of 4 is appropriate.

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 and resource: 'Clear the computation journal.' It uses a specific verb and resource, and the tool is distinct from siblings like 'clear_expression_cache' and 'clear_variables', which target different resources.

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 'get_computation_journal' or 'clear_expression_cache'. The agent is left to infer the appropriate context without explicit direction.

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