ai_clear

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the answered-only default and the mandatory confirmation flag, which implies a guarded destructive operation. However, it stops short of stating what is actually cleared, whether the action is reversible, or what happens when onlyAnswered is false.

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?

Three short fragments with no filler, front-loaded with the core action. It is appropriately terse for a two-boolean-parameter tool, though the brevity leaves some explanatory gaps.

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 destructive queue-clearing operation, the description is incomplete: there is no output schema, no statement of irreversibility, no explanation of what the AI queue represents, and no clarity on the effect of onlyAnswered=false. An agent can likely invoke it, but reliability and safety understanding are limited.

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%, so the description must compensate. It adds meaning by associating 'answered-only' with the onlyAnswered parameter and asserting that confirm must be true, which goes beyond the schema's default. Still, it does not explain the effect of confirm=false or fully define what 'answered-only' means in the queue context.

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 states a specific verb and resource: 'Bersihkan antrean AI' (Clear AI queue). This is not a tautology and identifies a unique resource distinct from sibling tools like ai_inbox, ai_reply, and ai_config, though it does not explicitly contrast with them.

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 about when to use this tool versus alternatives or what contextual conditions call for it. 'Requires confirm=true' is a parameter constraint rather than usage context, and there are no exclusions, prerequisites, or alternative routing.

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