signal_manage

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

No behavioral traits are disclosed. The description does not mention side effects, permissions, or whether operations are read-only or destructive. With no annotations, the description carries the full burden but provides zero transparency.

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?

The description is very short (two sentences) and front-loaded, but it sacrifices substance for brevity. While concise, it omits critical information needed for correct tool invocation.

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?

Given the tool's polymorphic nature (five sub-operations) and no output schema, the description is severely incomplete. It fails to explain any operation details, expected parameters, or return values, leaving the agent to guess.

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?

Even though schema coverage is 100%, the description adds no extra meaning beyond the schema. The parameter descriptions are minimal and generic (e.g., 'Operation in the signal branch'), and the tool description does not clarify what parameters should be used for each operation.

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 only states 'Godot signal operations', which is a broad category without specifying the action or resource. It fails to distinguish from sibling tools like node_manage or scene_manage. The reference to godot_catalog implies it is a dispatcher but does not clarify its purpose.

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 explicit guidance on when to use this tool versus alternatives. The only hint is 'Call godot_catalog for the operation tree', which is indirect and does not provide clear context for selection.

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