reset_seen

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

The description indicates a state-mutating operation ('clear') but provides no additional behavioral details such as side effects, reversibility, or permissions. With no annotations to rely on, this is adequate but minimal.

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 that is concise, front-loaded, and contains no superfluous information. Every word contributes to understanding.

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 parameterless tool with an output schema, the description is sufficiently complete. It explains the core action and effect. Minor improvement could be mentioning the output (e.g., confirmation).

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 the schema coverage is 100%. The description does not need to add parameter semantics, and it adequately explains the action. Baseline for 0 params is 4.

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's purpose: clearing the seen-set to reset the state for next_inspiration. It uses a specific verb ('clear') and resource ('seen-set'), and implicitly distinguishes from siblings like remove_from_inspiration and next_inspiration.

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?

While the description implies usage when a fresh start for next_inspiration is needed, it lacks explicit when-to-use or when-not-to-use guidance, and does not mention alternatives among siblings. Simple context but no directed advice.

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