Connect RFID badge bus

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

Annotations already indicate the tool is not read-only and not destructive; the description adds that it 'creates a scaffold' and lists the scaffold's contents, which provides some context. However, it does not disclose side effects or specific behavioral traits such as project modifications, file generation, or configuration implications beyond the scaffold itself.

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 enumerates the scaffold's contents without redundancy. It earns its place with every word.

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 nine parameters, no required fields, and low schema coverage, a one-sentence description is insufficient. It does not address return values, how the scaffold is delivered, or any post-creation behavior, leaving the agent without crucial operational context.

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%, and the description does not explicitly explain the meaning of the nine parameters. It lists components like 'sanitized badge events' and 'reader maps' which vaguely map to parameters, but offers no concrete guidance on parameter usage or defaults.

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 creates an RFID badge-reader scaffold and enumerates key components (sanitized badge events, reader maps, privacy policy, adapter source, access control safety notes). This distinctive focus differentiates it from the many sibling connect/create tools.

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 about when to use this tool versus alternatives. The description only states what it does, with no context about prerequisites, preferred scenarios, or exclusions.

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