pointcloud.list

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only says 'List' with no mention of read-only nature, return format, or side effects. The agent cannot tell if this is a safe operation or if it affects state.

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 extremely short and front-loaded ('List point cloud objects and data-blocks'). However, it lacks structure and could be more informative without significant bloat. Not excessively verbose, but borderline under-specified.

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 simple list tool with no parameters, the description is arguably complete in stating the core action. However, it omits context about what constitutes a 'data-block', and does not clarify when to use list versus report or other query tools. Given the number of sibling tools, more context would be beneficial.

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 zero parameters and 100% schema description coverage trivially. The description adds no parameter information beyond what the schema provides, which is nothing. Baseline 3 is appropriate.

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 ('List') and resource ('point cloud objects and data-blocks'), clearly stating the tool's action. It distinguishes from sibling tools like pointcloud.report and pointcloud.set, which imply different operations. The term 'data-blocks' is slightly ambiguous but not misleading.

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 on when to use this tool vs alternatives. For example, it does not explain how pointcloud.list differs from pointcloud.report or object.list (if it existed). The agent has to infer based on name alone.

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