Get Sitemap Info

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

No annotations are provided, so the description carries the full behavioral burden. It never says this is a read-only lookup, what authentication/permission scope the required user_id and host_id imply, or what happens if the sitemap_id does not correspond to an auto-detected sitemap. Only an output schema exists to cover return values.

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?

A single front-loaded sentence with no waste. Its brevity is appropriate given the 100%-covered schema, though the one-line form leaves no room for the disambiguating context the sibling set demands.

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 100% schema coverage, an output schema present, and no nested objects, the description is minimally sufficient to invoke the tool. However, for a tool in a crowded sitemap sibling cluster with zero annotations, it omits the routing and safety context an agent would benefit from.

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%, with all three required params (user_id, host_id, sitemap_id) documented in the schema itself, including host_id's format. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 ('get') and resource ('sitemap'), and the qualifier 'auto-detected' distinguishes it from the sibling get_user_added_sitemap_info without naming it. Clear, though it never explicitly routes the agent between sitemap-reading siblings.

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?

Usage is only implied by the phrase 'auto-detected sitemap', which hints at the contrast with user-added sitemap tools. There is no statement of when to prefer this over get_user_added_sitemap_info or get_sitemaps, and no prerequisites mentioned.

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