Set Layout Element Visible

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, and the description is consistent with them (no contradiction). The only added text is generic boilerplate about 'verifiable structured results' and 'write and path restrictions depend on service capabilities', which conveys no tool-specific behavior such as whether the change is persisted or requires a save_project call.

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 text is short but the second clause is generic filler ('write and path restrictions per service capability') that does not earn its place, while the essential information (visibility toggle, identifiers) is entirely absent. Brevity here is under-specification, not conciseness.

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?

An output schema exists so return values need not be explained, but for a 4-required-parameter mutation tool with zero schema coverage the description leaves the agent without the meaning of any parameter, the visibility semantics, or the prerequisite that the .aprx and layout be loaded.

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?

All four parameters (aprx_path, layout_name, element_name, visible) have 0% schema description coverage, and the description supplies no meaning for any of them — not even the boolean visible flag or the expected path format. The description completely fails to compensate for the coverage gap.

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 says only 'set layout' (设置布局), which restates a vague category rather than the actual action of toggling the visibility of a named layout element. An agent cannot distinguish this tool from siblings like set_layout_element_position, delete_layout_element, or layout_upsert_element without reading the tool name and schema.

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?

There is no when-to-use guidance, no prerequisites (e.g. project must be open, layout/element must exist), and no mention of alternatives such as set_layer_visible for map layers vs. layout elements. Nothing routes the agent to or away from this tool.

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