hide_object

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds no further behavioral context, such as whether the change is persistent, affects viewport only, or is reversible. It merely restates the basic visibility toggle without extra insight.

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, which is very concise and front-loaded. It avoids verbosity, though it lacks any structured breakdown of behavior or parameters.

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 simple action and existing output schema, the description is too minimal. It does not clarify the relationship between the 'hide' boolean and visibility states, nor does it provide enough context for a low-complexity tool. It leaves important parameter semantics ambiguous.

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 description does not explain the 'object_name' or 'hide' parameters. Since there are two parameters and no compensation from the description, the agent has no semantic understanding of what parameters do or how they interact.

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 'Sembunyikan/tampilkan objek' clearly states the tool hides or shows an object, using a specific verb and resource. However, it does not distinguish this from the sibling tool 'unhide_all', and the Indonesian phrasing may be ambiguous for agents expecting English.

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 like 'unhide_all' or 'select_by_type'. The description gives no context, prerequisites, or exclusions.

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