unhide_all

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

The description adds no behavioral context beyond the annotations. While annotations indicate destructiveHint=true and readOnly=false, the description does not explain what 'show' entails (e.g., affects both viewport and render visibility, impacts selected state, or is irreversible). No contradiction with annotations, but no added transparency.

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, short sentence with no fluff. It is front-loaded with the action and object. However, it is extremely terse, potentially sacrificing clarity for brevity.

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 tool with no parameters and an output schema, the description is minimally adequate. However, it omits important context such as the scope of 'all objects' (scene-wide? visible layers?), potential side effects, and whether it returns a confirmation or count. Given the destructive hint, more context would help the agent assess consequences.

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 tool has zero parameters, so the schema requires no explanation. The description's simplicity is appropriate; there is no parameter information to supplement.

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 'Tampilkan semua objek' clearly states the action (show) and resource (all objects), and the tool name 'unhide_all' reinforces its purpose. It distinguishes from siblings like 'hide_object' and 'delete_object', though it could be more explicit about 'unhiding' rather than 'showing'.

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. It doesn't mention prerequisites, such as whether objects need to be hidden first, or contrast with other visibility-related tools like 'select_by_type' or 'hide_object'.

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