List Objects

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

No annotations are provided, so the description carries the full behavioral burden, yet it omits that this is a read-only operation, says nothing about pagination or result-size limits, and does not explain how the optional session_key affects targeting. It only restates the filtering behavior already visible in the schema.

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?

A single tight sentence with the resource front-loaded and the optional filtering trailing. No filler or redundancy, though it is arguably too terse for a tool with three parameters and no annotations.

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?

An output schema exists, so return values need not be explained, and the parameters are fully documented in the schema. The remaining gap is routing: with 20 siblings, the description never explains when this listing tool is the right choice over get_selection or get_scene_info.

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 100%, so the schema already documents pattern (wildcard on names), session_key, and type_filter with its enum values. The description echoes the type/name filters but adds no syntax, wildcard-format, or default-behavior detail beyond the schema, so baseline 3 applies.

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?

Clear verb+resource: 'List scene nodes' states exactly what is returned, and it names the two filtering dimensions. It does not, however, distinguish itself from siblings like get_selection or get_scene_info that also enumerate scene entities, so an agent must infer the boundary.

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 says the filters are optional but never states when to reach for this tool versus get_selection, get_scene_info, or select_objects. There is no context, prerequisite, or exclusion guidance — only a restatement of the parameter behavior.

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