find_signal_connections

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

Absence of annotations places the burden on the description. It implies a read-only operation ('find') but does not disclose any behavioral traits (e.g., whether it returns a list, includes subscenes, or has side effects). No mention of nondestructiveness beyond the verb itself.

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?

A single, short sentence that conveys the core purpose without extraneous information. Every word is necessary.

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 tool with no parameters and no output schema, the description is functional but lacks depth. It does not clarify what constitutes a signal connection, scope boundaries (current scene vs. all scenes), or the format of the result. Slightly below adequate given the simplicity.

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?

No parameters exist, so the input schema fully covers them. The description adds no parameter-specific meaning, but the baseline for zero parameters is 4. It correctly implies the tool operates on the whole scene without filters.

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 clearly states the action (find) and resource (signal connections) with a scope (in the scene). It distinguishes from siblings like connect_signal and disconnect_signal, but lacks explicit differentiation from analyze_signal_flow.

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 on when to use this tool versus alternatives such as get_signals or analyze_signal_flow. No context on prerequisites or exclusion criteria.

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