Create NCAM camera tracking bus

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

Annotations already indicate readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is known. The description adds that it creates a scaffold with certain maps, but does not disclose any side effects, prerequisites, or runtime behavior beyond creation. No contradiction with annotations.

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 core purpose. It earns its place without unnecessary verbosity, though it sacrifices informative detail for brevity.

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 7 parameters, only 29% schema coverage, no output schema, and a large sibling set, the description is far too sparse. It does not explain what a 'scaffold' entails, how parameters affect the result, or what the agent should expect after invocation. The agent cannot confidently invoke this tool correctly.

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 29% (2 of 7 parameters have descriptions). The description mentions map types (pose, lens, video-preview, calibration) but does not explain any parameter semantics. With low schema coverage, the description should compensate by explaining key parameters like port, active, camera_count, and lens_profile_count, but it does not.

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 identifies the resource (NCAM camera-tracking scaffold) and lists the included maps (pose, lens, video-preview, calibration). It is specific to this tool and distinguishes it from other tracking-bus tools by name and content, though it does not explicitly contrast with siblings such as create_blacktrax_tracking_bus.

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 no guidance on when to use this tool versus alternative tracking-bus creation tools. Given the large number of sibling tools (e.g., create_optitrack_tracking_bus, create_blacktrax_tracking_bus), the lack of explicit usage context or exclusions is a notable gap.

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