pixoo64_send_text

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

No annotations exist, so the description carries the load, and it discloses key behavior: it mutates/replaces an existing overlay, requires a prior animation to exist, and backgroundColor triggers a solid 64×64 background first. It omits what happens to other existing overlays and the response shape, but the state dependencies and side effects are well covered for a mutation 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?

Four compact sentences, front-loaded with the core action, followed by prerequisites and device constraints. Each clause carries useful information with little padding, though the device/firmware constraints are densely stacked without clear grouping.

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 complex nested-parameter mutation tool with no annotations and no output schema, the description covers hardware and state requirements well but leaves the meaning of several text sub-fields and the return behavior unaddressed. An agent can call it but may misconfigure TextId or dimensions.

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 only 33%, and many nested text fields (TextId max 19, x/y, TextWidth, color, align, dir, speed) are undocumented anywhere. The description clarifies backgroundColor's effect and target.hardware's meaning, but the font range 0–7 merely restates the schema's min/max and TextId replacement semantics are only hinted at.

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?

"Add or replace a text overlay using Draw/SendHttpText" states a specific verb and resource and names the underlying command. It distinguishes itself from related siblings like pixoo64_clear_text and timegate_send_text by the PIXOO64 hardware constraint, though it doesn't explicitly route away from 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?

Gives concrete prerequisites: requires a previously sent animation, legacy firmware needs 90102+, and hardware must be 90/92/96. It explains how to supply target.hardware or discover it. It stops short of explicitly naming alternatives like pixoo64_send_items for non-text overlays.

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