scene-update-game-object-filters

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

No annotations are provided, and the description does not disclose behavioral traits such as whether filters are replaced or merged, whether changes are reversible, or what 'parent game objects' means. The description is too minimal to inform safe usage.

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, which is concise but misleading (says 'add' when tool is 'update'). It lacks structural clarity and fails to convey the tool's actual behavior.

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?

Given the tool has nested parameters, many sibling tools, no output schema, and no annotations, the description is severely incomplete. The agent cannot determine proper usage, expected outcomes, or how this tool fits with other scene filter tools.

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 50% (sceneId and id have descriptions; internal has a description; type is an enum; properties references system prompt). The description adds no additional meaning beyond the schema; for example, it does not clarify the relationship between 'id' and 'type' or how properties are applied.

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 'Add multiple filters' but the tool name is 'update-game-object-filters', and the schema's property 'id' is described as 'The id of the filter to update', indicating an update operation. This contradiction confuses the tool's purpose. Additionally, there is a sibling tool 'scene-add-game-object-filters' for adding, so the description fails to distinguish the tool from alternatives.

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 guidelines are provided on when to use this tool versus alternatives like scene-add-game-object-filters or scene-delete-game-object-filters. The agent is given no context about which scenarios call for update vs. add vs. delete, leaving it to guess.

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