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

The description says 'Preview publishing or unpublishing,' which strongly implies a read-only dry run, but annotations declare readOnlyHint=false and the tool name indicates a real change. This is a material contradiction, and the description adds no other behavioral context such as side effects, reversibility, or required permissions.

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 filler, so it is concise. However, that conciseness comes at the cost of under-specification, and the sentence does not front-load the key facts an agent needs.

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 three-parameter mutation tool with no output schema and no parameter descriptions, the definition is substantially incomplete. It does not explain what visibility change is being previewed, what the resource types are, or whether any real state is modified.

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 mention resourceId, resourceType, or visibility at all. The schema has enums for visibility and resourceType, but the description provides no added meaning or usage guidance for these required parameters.

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 'Preview publishing or unpublishing a resource,' which is specific in verb and resource but inconsistent with the tool name and title ('Change resource visibility'). It does not mention visibility values or resource types and gives no sibling differentiation, so an agent could easily confuse it with a dry-run preview rather than a visibility mutation.

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 guidance on when to use this tool versus alternatives such as resource_share_grant, resource_delete, map_publish, or project_set_layer_visibility. The only context is the ambiguous word 'Preview,' which does not clarify when this operation should be selected.

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