Connect GTFS transit feed

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

Annotations declare readOnlyHint=false and openWorldHint=true, implying the tool may create resources and interact with external data. The description adds that the scaffold includes an 'adapter source' and 'public-data notes', suggesting possible external data interactions, but it does not disclose specifics like network calls, file creation, or setup behaviors. With annotations covering the basic safety profile, the description provides modest additional context.

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 a single, efficient sentence with no fluff. It front-loads the main action and then lists key deliverables. It is appropriately concise, though a bit dense; a structured list could improve readability, but it earns its place.

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 9 parameters, no output schema, and no nested objects, the description is too brief to cover important context such as return values, the nature of the 'adapter source', whether data is fetched live or simulated, or how the scaffold integrates with the existing network. The description does not explain what the final result looks like or how parameters influence it, leaving significant ambiguity for an agent selecting and configuring this tool.

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 only 22% (2 of 9 parameters documented), and the tool description does not mention parameters at all. Parameter names like stop_count, route_count, and prediction_count are somewhat self-explanatory, but 'active', 'feed_mode', and 'adapter_url' lack meaningful context. The description lists output artifacts but does not map them to input parameters, leaving the agent to infer how each parameter affects the scaffold.

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 a specific action ('Create') and resource ('GTFS static/realtime transit scaffold'), listing concrete components (route maps, stop maps, arrival predictions, adapter source, public-data notes). This distinguishes it from siblings like connect_casparcg_server or create_data_source, as it is uniquely scoped to GTFS transit feeds.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites, exclusions, or related tools. In a large sibling set of connect_* and create_* tools, the description does not help the agent decide when this is the right choice.

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