timegate_clear_text

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

No annotations exist, so the description carries the full burden. It usefully discloses that custom display-list dials are NOT deleted and that the device has five independent screens, but it omits permission/auth requirements (the localToken) and says nothing about the response or failure behavior.

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 compact sentences that lead with the action, then the clearing semantics, then the scope caveat and hardware constraint. Dense but front-loaded with no filler.

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?

With no annotations, no output schema and a nested target object, the description covers purpose, hardware scope and one destructive-vs-non-destructive distinction, but leaves auth expectations and return behavior entirely to inference.

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 coverage is 50%. The description adds real meaning for textId (-1 clears all) and implies lcdIndex maps to one of five screens. It says nothing about localToken or the nested target override, leaving half the parameters to the schema alone.

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?

States a specific verb and resource ('Clear animation text') plus the protocol call behind it (Draw/ClearHttpText and LcdId). The TimeGate 400/402 constraint and the 'five independent 128x128 screens' note effectively separate it from the PIXOO64 clear-text sibling, though no sibling is named directly.

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?

The hardware restriction ('TimeGate Hardware 400/402 only') implicitly routes the agent away from pixoo64_clear_text, and textId=-1 gives a clear usage pattern for clearing everything. However there is no explicit when-to-use vs. when-not guidance or mention of alternatives for partial clears.

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