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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the index-vs-child-sitemap relationship but says nothing about pagination behavior, rate limits, or what a 'URL record' contains; with output schema present the return detail gap is minor, so a 3 fits.

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 short sentences, zero filler, and the core action is front-loaded before the dependency note. Every clause carries information 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 low-complexity, zero-required-param listing tool with a full output schema and read-only annotations, the description plus schema covers everything an agent needs: what it returns, which param scopes it, and the discovery step to run first.

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 100%: both `type` (with all allowed values and the 'all' default) and `limit` (default 50, max 250) are fully documented in the schema. The description adds no syntax or constraint detail beyond what the schema already provides, so the baseline 3 is appropriate.

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?

Specific verb (Fetch) plus resource (URL records from a Rebag child sitemap) with a scoping qualifier ('matching its type'). It also indirectly distinguishes itself from rebag_sitemaps by pointing to that tool as the index/discovery step, though it never explicitly contrasts the two outputs.

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?

'Use rebag_sitemaps to discover the index and child sitemap URLs' establishes the prerequisite step and effectively names the alternative tool. It gives clear context for when to use it, but offers no exclusion (e.g., when you should skip this and go straight to product/page tools).

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