ywm_get_sitemap

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Get sitemap details' without indicating whether it's read-only, requires authentication, or has rate limits. The description adds no transparency beyond the tool's name.

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 concise sentence, which is brief and front-loaded. However, it is so minimal that it sacrifices informativeness for brevity; it could expand slightly without losing conciseness.

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?

Given the tool's simplicity and lack of output schema, the description should at least hint at the return value (e.g., 'Returns metadata about the sitemap'). It does not, leaving agents uninformed about the result. Schema coverage is good but context is incomplete.

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?

Both parameters are fully described in the input schema (100% coverage), so the description does not need to add parameter meaning. The description's 'details' is generic and doesn't elaborate on what parameters retrieve, but the schema suffices. 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?

The description 'Get sitemap details' specifies the verb and resource, distinguishing it from sibling tools like list or add. However, it is vague about what 'details' entails and could be more specific by mentioning 'for a given sitemap ID'.

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?

The description provides no guidance on when to use this tool versus alternatives such as ywm_list_sitemaps, nor does it mention prerequisites or context. An agent would lack direction on its appropriate use.

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