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 that the read is scoped to a single child sitemap selected by type, but says nothing about rate limits, pagination, or result size beyond what the schema supplies. Adequate against an already-covered annotation baseline.

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 tight sentences with zero filler. The scoping purpose is front-loaded, and the second sentence is a pure routing instruction that earns its place.

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 no explanation, and annotations cover the safety profile. The description supplies purpose, scope, and the prerequisite sibling, leaving only minor gaps like pagination behavior for large sitemaps.

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%, so both parameters (type and limit) are fully documented in the schema, including the allowed type values and the limit default/max. The description only echoes the type-based scoping ('by sitemap type') without adding syntax or format meaning, so baseline 3 is correct.

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?

States a specific verb (Fetch), resource (sitemap URL record rows), and scope (one Brooklinen child sitemap, filtered by sitemap type). This clearly distinguishes it from the sibling brooklinen_sitemaps (which returns the index/child sitemap list) without opening either 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?

Names the sibling brooklinen_sitemaps and states the workflow prerequisite: use it first to discover the index and child sitemap URLs. That is clear routing context, though it does not give an explicit 'when not to use' condition.

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