signals

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

The description lists actions that imply mutation (connect/disconnect), which aligns with the destructiveHint annotation. However, it does not add behavioral details beyond the actions themselves, such as error handling, permission requirements, or side effects.

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 extremely concise, using a structured list format that is easy to parse. Every sentence adds meaningful information, and the format front-loads the key actions.

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 multiple actions and parameters, the description is adequate. It covers the main functionality and parameter usage. However, without an output schema, some context about return values or error conditions could be helpful.

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?

The input schema already provides 100% description coverage for all 8 parameters. The description adds value by explaining which parameters are required versus optional for each action, going beyond the schema's flat listing.

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 tool manages signal connections and lists three specific actions (list, connect, disconnect) with their parameters. It distinguishes itself from siblings by focusing exclusively on signals, which is a focused domain.

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?

The description provides a minimal usage guide by showing required parameters for each action, but it does not explicitly tell the agent when to use this tool versus alternatives or when not to use it. There are no exclusions or context about prerequisites.

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