Click a GuiButton

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds what actually happens: it writes live game state, runs any connected handler, requires the executor's firesignal, and degrades with a clear { error } when unavailable. It also names the failure path and a verification tool (get-gui-text), which is well beyond the annotation coverage.

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?

Front-loaded with the critical warning 'WRITES LIVE GAME STATE' and flows logically through mechanism, usage, behavior, and return shape. The trailing Phase/cost/capabilities metadata (e.g. idempotency=contextual-write, Capabilities: firesignal) is somewhat redundant and could be trimmed, keeping it just under the top mark.

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 output schema, the description compensates by describing the return shape ({ Path, Fired, ok } or { error }), the prerequisites, the degradation path, and a verification step. An agent has everything needed to invoke it correctly and interpret the result.

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 100%, so the baseline is 3, but the description adds meaning: it spells out the signature and lists the exact signals fired when action is omitted (Activated, MouseButton1Down, etc.), which the schema only summarizes. It does not add much for threadContext beyond the schema.

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 (click) and resource (Roblox TextButton or ImageButton) and explains the exact mechanism: firing GUI signals via firesignal so connected handlers run. This distinguishes it from siblings like fire-signal and virtual-input, which operate at a lower level.

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 a clear condition: 'Use when direct UI activation is needed inside the active client,' plus prerequisites (active-client, resolved-target, explicit-mutation-approval). It does not explicitly name the alternative tool (e.g. virtual-input or fire-signal) an agent should pick instead, so it stops short of full when-not guidance.

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