gsc_track_sitemap_deltas

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

No annotations are provided, so the description carries the behavioral disclosure burden. It explicitly says 'Read-only' and 'no state is written', which clearly signals a safe, non-mutating operation. It doesn't cover rate limits or authentication, but the core side-effect profile is transparent.

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?

Two sentences with the most important information front-loaded: the tool is read-only, it fetches a snapshot, it compares to a baseline, and it writes no state. Every clause earns its place with no filler.

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?

With no output schema and no annotations, the description is too thin: it doesn't describe the shape of the returned deltas or how the output is meant to be used as a future baseline. It also omits guidance on the behavior of includeUnchanged and minAbsIndexedDelta, leaving an agent to infer important filtering behavior.

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?

With 75% schema description coverage, the schema already documents siteUrl, baseline, and minAbsIndexedDelta. The description adds only minimal parameter-level context by labeling the baseline as 'agent-provided', and it does not clarify includeUnchanged, which lacks a schema description.

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?

Clearly identifies the operation: a read-only sitemap delta tracker that fetches the current sitemap snapshot and compares it to an agent-provided baseline. It specifies the resource (sitemap) and action (fetch/compare), but does not differentiate it from sibling sitemap tools such as gsc_list_sitemaps or gsc_get_sitemap.

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 implies the use case—comparing a current snapshot to a baseline to detect deltas—and notes no state is written. However, it provides no explicit when-to-use/when-not-to-use guidance or alternatives among the many sitemap/indexation sibling tools, so an agent may need to infer the right context.

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