Dump the constants of a connection's handler function

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

Annotations already declare read-only/idempotent/non-destructive, and the description reinforces this while adding real behavioral detail: prerequisite functions, a clear { error } on missing deps or no Lua Function, the value-encoder output behavior, and the exact return shape. The one oddity is 'Produces: created-handle' for an otherwise read-only operation, but that is not a direct contradiction.

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-loads the core action and rationale in the first two sentences, then layers prerequisites, return shape, and metadata. The trailing block (Phase, cost, Requires, Capabilities, Produces, Safety, On failure) is dense and somewhat templated but each line carries usable information, so it earns most of its length.

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 supplies the full return shape ({ Signal, ConnectionIndex, Function, Constants, Count }), failure behavior, prerequisites, and the caveat that non-Lua or missing connections produce { error }. Nothing an agent needs to invoke it correctly is missing.

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 schema already documents all four parameters including the zero-based connectionIndex and the signalName/instancePath relationship. The description largely restates this (signature line, zero-based index note) rather than adding new semantics, so the baseline 3 is appropriate.

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+resource: disassemble the Lua function bound to ONE connection on an RBXScriptSignal and return its constant pool via debug.getconstants. The scope (one connection, selected by index) and the underlying primitive distinguish it from siblings like get-connection-upvalues, get-closure-constants, and get-connection-protos.

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 clear context for when the tool matters (reverse-engineering hidden event handlers, e.g. which RemoteEvent names or HTTP endpoints are touched) and names prerequisites (getconnections, debug.getconstants) plus the upstream tool (list-signal-connections) for the index. It doesn't explicitly contrast itself against the closest alternatives (e.g. get-connection-upvalues or trace-connection-function), so it stops short of a 5.

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