flash

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

No annotations are provided, so the description must fully convey behavioral traits. 'Toggle' implies state change but does not disclose whether it is destructive, reversible, or requires permissions. The agent cannot infer the impact of calling this tool.

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 extremely concise at 4 words, which is efficient. However, it may be too terse, sacrificing explanatory value. It is front-loaded but costs completeness.

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 no annotations, output schema, or parameters, the description carries the sole burden of explaining the tool. It does not define 'semantic flashbacks', the effect of toggling (on/off), or how this interacts with other tools. The description is insufficient for an agent to use the tool correctly.

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 coverage is 100% by default. The description adds no parameter information, but none is needed. According to the rubric, baseline is 4 for 0 parameters.

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 'Toggle semantic flashbacks' provides a clear verb-resource pair indicating the tool toggles a feature called 'semantic flashbacks'. It is specific enough to distinguish from basic CRUD tools, but lacks explanation of what 'semantic flashbacks' are, which might be ambiguous.

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 given on when to use this tool versus siblings like 'forgotten', 'get_context', or 'reset'. The description does not mention prerequisites, side effects, or alternative tools.

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