get_sitemap

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

No annotations exist, so the description carries the safety disclosure burden. 'Retrieve' implies a non-mutating read operation, which is useful, but the description does not disclose authentication requirements, rate limits, or what counts as an error metric. It is not misleading, but it is thin on 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 sentence with no filler, repetition, or structural clutter. It front-loads the verb and object, making the tool's core purpose immediately scannable.

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?

There is no output schema, and the description does not compensate by explaining what 'deep indexing and error metrics' concretely include or how the response is shaped. Combined with absent annotations and no usage/alternative hints, the picture is incomplete for an agent that must interpret the returned metrics.

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 all three parameters already carry semantic descriptions in the schema. The tool description adds no additional parameter-level meaning beyond restating that the feed is a sitemap, so it does not go beyond the schema baseline.

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 states a clear action ('Retrieve') on a specific resource ('a specific sitemap feed') and names the output domain ('deep indexing and error metrics'). It can be distinguished from siblings like list_sitemaps by the focus on a single feed, but it does not explicitly name alternatives or state exclusions, so it stops short of full differentiation.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The phrase 'specific sitemap feed' hints at the intended scope, but the description never directs the agent to list_sitemaps for enumeration, inspect_url for individual URLs, or otherwise states trade-offs between sibling tools.

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