unhide_objects

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

Annotations already provide readOnlyHint=false and destructiveHint=true, so the destructive nature is disclosed structurally. The description adds one meaningful behavioral detail: omitting 'objects' unhides everything. However, it does not explain side effects, state changes, or interaction with hide_objects beyond the basic visibility toggle.

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 short and front-loaded with the key behavior. The bilingual duplication is slightly redundant but understandable given the localization context, and it does not add excessive length.

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 simple one-parameter tool, the description is mostly sufficient and it covers the default behavior. However, it does not mention the relationship with sibling tools like unhide_all, which could lead to ambiguity when an agent decides which tool to invoke. There is also no indication of return values, though the absence of an output schema reduces that burden.

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 schema's parameter description only says 'Objects to show.' The tool description adds crucial semantics: if 'objects' is omitted, all hidden objects are shown. This goes beyond the schema and clarifies the parameter's optionality and default behavior.

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 ('show') and the resource ('the given objects' or 'all'), with a specific conditional behavior. It is easy to understand what the tool does, but it does not explicitly distinguish itself from the sibling tool unhide_all, which also relates to making objects visible.

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?

The description provides an implied usage rule ('show all if none specified') but gives no explicit guidance on when to use this tool versus the alternative unhide_all. It does not mention exclusions, requirements, or scenarios where another tool would be preferred.

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