spatial_compare_remote

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the tool interacts with a remote spatial-service, but it does not disclose what 'compare' entails (e.g., network requests, metadata-only diff, side effects like caching). Given annotations, the description provides some additional context but not deep behavioral detail.

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, front-loaded sentence with no filler or redundancy. It states the primary action and target efficiently, making it easy for an agent to grasp the tool's purpose at a glance.

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?

The tool has one parameter, simple purpose, and a read-only annotation profile, so the description is mostly adequate. However, with no output schema, the agent does not know what 'compare' returns (e.g., a diff list, a summary). Given the low complexity, the missing return semantics and prerequisites (e.g., network access) represent a moderate gap.

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%, so the description must compensate for the single remoteUrl parameter. The example URL gives a concrete format and hints that the parameter expects a spatial-service base URL, but it does not explain how the URL is used or what constitutes a valid endpoint. The description partially compensates with the example but leaves room for ambiguity.

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 uses a specific verb 'Compare' with a clear resource ('layers and fields here') and target ('another spatial-service'), and the example URL clarifies what constitutes a remote service. This distinguishes it from siblings like spatial_import_from_remote (import vs compare) and spatial_list_layers (local listing vs cross-service comparison).

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 no explicit guidance on when to use this tool versus alternatives, nor any exclusions. The example URL suggests a use case, but there is no mention of, for instance, 'use this when you need to verify schema parity before importing' or 'not for comparing data contents'. Agents must infer the intended usage solely from the verb.

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