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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not say what kind of details are returned, whether the call is scoped to a verified property, or how it behaves for sitemaps that exist but were never fetched.

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 short sentence that is front-loaded and waste-free, but the brevity comes at the cost of information rather than being earned through efficiency. There is no structure beyond the bare statement of purpose.

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 not be explained, but the two required inputs carry no semantics anywhere in the definition. For a two-parameter lookup tool with zero schema coverage, the description should at minimum explain what feedpath and site_url must contain to avoid failed calls.

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 0%, so both required parameters are undocumented in the schema, and the description does not compensate. In particular, feedpath is ambiguous (full sitemap URL versus path? relative or absolute?) and site_url is presented without saying whether it must match a verified Search Console property.

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 (details of a single sitemap), and the word "single" implicitly contrasts it with the sibling list_sitemaps that returns many. The only gap is that "details" is left undefined, so the agent knows what object it targets but not what information it returns.

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?

There is no when-to-use guidance, no prerequisite (e.g., needing site_url/feedpath obtained from list_sitemaps), and no note on failure behavior for unknown sitemaps. The agent must infer usage purely from the name and from the existence of list_sitemaps in the sibling set.

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