pointcloud-attributes

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

No annotations are provided, so the description must disclose behavioral traits. 'List point cloud geometry attributes and color attributes' implies a read-only listing operation, but it does not specify output format, side effects, or limitations (e.g., whether it requires an active point cloud, performance implications). The description is too terse to convey behavioral expectations beyond the basic action.

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 clearly states the action (list) and the targets (geometry attributes and color attributes). It is front-loaded and contains no filler. However, it lacks a brief note on usage context, but given the single-sentence constraint, it's reasonably concise.

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 one parameter and no annotations, the description is minimal. It doesn't explain what 'attributes' includes (e.g., position, normals, UVs, vertex colors?), nor does it mention any prerequisites like requiring a selected point cloud. Given siblings like pointcloud-report (which might give a broader view) and pointcloud-set, the description is incomplete for an agent to decide when to use this vs 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?

The input schema has one parameter 'name_or_object' described as 'Point cloud object or data-block name'. Schema description coverage is 0%, meaning the schema property lacks a description. The tool description does not explain what values are acceptable, how the parameter should be formatted, or whether it accepts a name or an object reference. The description adds minimal semantic value beyond the schema's 'title' field.

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 states the tool lists point cloud geometry and color attributes, which identifies the resource (point cloud) and verb (list). However, it doesn't distinguish from sibling tools like pointcloud-report or pointcloud-set, and 'attributes' is somewhat ambiguous (could include position, normals, UVs, etc.).

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 explicit guidance on when to use this tool versus alternatives like pointcloud-report or pointcloud-set. The description does not mention typical use cases, prerequisites, or scenarios where this tool is preferred. Sibling tools covering similar ground (pointcloud-report, pointcloud-set) make the lack of differentiation a notable gap.

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