Connect parking occupancy bus

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

The description adds context about what the scaffold includes (zone occupancy, sensor maps, signage policy, adapter source, privacy safety notes). With readOnlyHint=false and destructiveHint=false, the write-but-non-destructive nature is consistent, but no additional behavioral details like side effects or return format are disclosed.

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 concise sentence that front-loads the primary action and resource. The list of components is relevant and not wasted, though it is slightly jargon-heavy.

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 10 parameters, no required fields, no output schema, and many similar siblings, this description is too high-level. It does not explain the structure of the scaffold, what a 'bus' means, or how the parameters interrelate, leaving significant ambiguity.

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 20% (2 of 10 parameters described). The description does not compensate by explaining how its listed components map to parameters like capacity, provider, zone_count, or adapter_mode. The parameter names are self-explanatory but the description adds little semantic meaning beyond them.

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 uses a specific verb ('Create') and resource ('parking/queue occupancy scaffold') with a clear list of components. It is reasonably differentiated from siblings like connect_queue_length_bus, though it does not explicitly name alternatives.

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 is given on when to use this tool versus similar siblings (e.g., connect_people_counting_bus). The description only states what it does, leaving usage context entirely implied.

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