scene-add-game-object-filters

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

No annotations are provided, so the description must fully disclose behavior. It only states a write operation ('Add') without mentioning prerequisites (e.g., parent object must exist), side effects, or whether filters are appended or overwritten. This is insufficient for a mutation tool.

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 efficiently conveys the action and target. No unnecessary words. It could be longer to improve completeness, but as a concise statement it succeeds.

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's complexity (multiple filter types, nested parameters) and the presence of sibling tools, the description lacks critical context: what happens to existing filters, how properties relate to filters, and any return values. It is not complete enough for an agent to use safely.

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?

With schema description coverage at 50%, the description should compensate by explaining parameters. It does not mention sceneId or objects at all, adding no value beyond the schema. The schema already provides some descriptions, but the description fails to clarify the connections or constraints.

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 clearly states the action ('Add multiple filters') and the target resource ('parent game objects in the scene'), distinguishing it from sibling tools like scene-delete-game-object-filters or scene-add-game-objects. However, it could be more specific about whether it appends to existing filters or replaces them.

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 is provided on when to use this tool versus alternatives such as scene-update-game-object-filters or scene-delete-game-object-filters. The agent receives no context for decision-making.

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