Extend data source fabric

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

Annotations indicate non-destructive and open-ended behavior. The description adds context by explaining that the tool builds a sub-network, produces a Null DAT and Null CHOP, and details how each transport works. This goes beyond the annotations, providing valuable behavioral insight.

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 concise, consisting of three sentences that front-load the main purpose and key details. It is efficient and avoids unnecessary elaboration, though it could be slightly more structured.

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 complexity of 14 parameters and no output schema, the description adequately covers the high-level behavior, including the output shape (Null DAT and Null CHOP). It could mention more about error states or default behaviors, but it provides sufficient context for an agent.

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 has 100% description coverage, so the baseline is 3. The description adds marginal value by summarizing the transport types and the downstream shape, but it largely repeats what the schema already says. No significant new meaning is provided 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?

The description clearly states that the tool adds extra transports to the data-source fabric, listing specific transports (mqtt, ws-binary, midi-mmc) with brief explanations. It distinguishes itself from the sibling tool 'create_data_source' by noting it goes beyond that, making the purpose specific and unambiguous.

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 implies usage for adding specific transports beyond the initial creation, but it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusion criteria or prerequisites. The guidance is implicit and could be improved.

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