Create ZED depth bus

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, aligning with the 'Create' action. The description adds the behavioral detail of 'runtime-gated warnings,' which is beyond the annotations, but it does not explain what conditions gate the warnings or what consequences the scaffold creation may have. No contradiction exists.

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 sentence with no filler, front-loading the action and resource. However, it relies on domain jargon ('TOP/CHOP/SOP placeholders') that may confuse users, slightly reducing clarity without adding length.

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 and no output schema, the description is too sparse to fully contextualize the tool's behavior, parameter relationships, or the nature of the runtime warnings. It does not explain what the scaffold contains, how it is used, or why a user would invoke this tool over simpler alternatives.

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 coverage is only 29% (only 'name' and 'parent_path' have descriptions), and the tool description provides zero parameter-level explanations. Parameters like 'body_count', 'stream_count', and 'include_pointcloud' remain ambiguous, and the description does not bridge the gap left by the sparse schema descriptions.

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' with a clear resource: 'ZED camera depth/body/point-cloud scaffold.' It also mentions ZED TOP/CHOP/SOP placeholders and runtime-gated warnings, which distinctly identifies the tool's function and separates it from similar depth-bus creation tools for other cameras (e.g., realsense, azure_kinect).

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 creating a ZED-based depth/body/point-cloud scaffold, but it does not explicitly state when to prefer this tool over alternatives or provide any exclusions. The context from sibling tools suggests a family of camera bus creators, yet the description offers no guidance on selection criteria.

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