faf_clear

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

No annotations provided, so description must fully convey behavioral traits. It implies destructive actions ('clear', 'reset', 'fresh start') but does not explicitly state that data is permanently deleted, whether user data is affected, or if confirmation is needed. There is no contradiction with annotations (none provided).

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 a single, clear sentence with no unnecessary words. It is front-loaded with the verb and resource, making the tool's purpose immediately apparent.

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?

While the parameters are simple and fully described, the tool is potentially destructive with no output schema. The description lacks behavioral context, such as what exactly gets reset, whether it affects other users, or how to revert. Given the number of sibling tools, additional guidance on typical use cases would improve completeness.

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 100%, so the baseline is 3. The description adds no extra meaning beyond the schema; it only restates the overall purpose without detailing parameters. Each parameter is already well-documented in the schema with booleans and short descriptions.

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 it clears caches, temporary files, and resets FAF state for a fresh start. The verb 'clear' and noun 'caches/temp files/state' are specific. However, among siblings is 'rag_cache_clear' which also clears caches, but the description mentions 'FAF state' to differentiate, though not explicitly.

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 like 'faf_init' or 'rag_cache_clear'. It does not specify prerequisites, when it is appropriate, or when not to use it. The agent is left to infer usage from name and description.

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