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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so safety is covered. The description adds two genuine behavioral facts beyond the annotations: the newest-patch default and the English fallback when a translation is missing. It does not cover ordering details, pagination, or error behavior for unknown patches.

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 compact sentence chain with no waste; the default ordering is front-loaded and the format hint follows immediately. The leading 'Site' qualifier is the only mildly ambiguous element.

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?

For a read-only, two-optional-parameter lookup with no output schema, the description covers the essentials: what it returns, the default selection, the accepted patch format, and the localization caveat. It is thin on return shape and invalid-input handling, but annotations and the low complexity limit how much more is needed.

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 the description must carry the load and it does partially: it gives the accepted patch string formats ('26.20' or '26-20'), confirms newest is the default when 'patch' is omitted, and explains the consequence of an unavailable translation for 'locale'. Neither parameter is named directly, so the mapping is inferential rather than explicit.

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 names the resource ('Site patch notes') and implies a listing ordered newest-first, but never supplies a verb such as 'retrieve' or 'list'. An agent can guess the intent, yet the phrasing is closer to a fragment than a stated purpose. Siblings are different resources entirely, so no sibling differentiation is needed or provided.

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?

'Newest by default' hints that this is the right tool for the latest notes and that the patch argument is optional, but there is no explicit when-to-use, no when-not-to-use, and no alternative named. The agent must infer that omitting 'patch' yields the current patch.

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