wb_favorites_list

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

No annotations are provided, so the description carries the full burden. 'List' implies a read-only, non-destructive operation, but nothing is said about whether the root must exist, whether results are paginated or cached, or what the response contains, and there is no output schema to fill that gap.

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 front-loaded sentence with no wasted wording. It is concise, though the brevity comes partly at the cost of the missing parameter and behavior details rather than from efficient information packing.

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 no annotations, no output schema, and an undocumented required parameter, the description does not supply enough for an agent to call this confidently. It should at minimum explain the root parameter and whether the return is a category list or usable prefab handles.

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 0%, and the single required parameter world_builder_root is a bare string with no documented format or meaning. The description never mentions the parameter, so an agent gets no help on whether it is a path, a project root key, or whether it must be an existing directory.

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?

States a specific verb ('List') and resource ('World Builder native Favorite categories'), which an agent can distinguish from the sibling wb_favorite_add that mutates favorites. The parenthetical '(reusable object/group prefabs)' clarifies what a favorite is, though it leaves slight ambiguity about whether categories or the individual items are returned.

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 when-to-use guidance, no prerequisites, and no mention of the related wb_favorite_add sibling or how to go from a category listing to spawning a prefab. The agent must infer that this is the discovery step before other favorite/prefab operations.

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