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

Annotations already declare readOnlyHint: true, so the tool is known to be a safe read operation. The description adds context by explaining version resolution (draft, historical, or published default), which is valuable. However, it does not disclose other behavioral aspects such as error handling, what 'elemental content' exactly returns, or any implications of the journey-scoped context. Since annotations cover safety, this is adequate but not comprehensive.

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 concise and well-structured: two sentences, the first stating the core purpose and the second providing version usage. It front-loads the primary action and avoids redundancy or unrelated details. Every sentence contributes meaningful information with no filler.

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 that the tool has a read-only annotation, no output schema, and 3 parameters (2 required), the description covers the essential usage: what it fetches and how to specify versions. It does not explain the return format or contrast with very similar siblings, which might be helpful but is not critical for a simple fetch operation. The description is sufficient for an agent to call it correctly for most scenarios.

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 are already documented in the schema with descriptions. The description adds minimal value by reaffirming the default version behavior ('Defaults to published'), which is already stated in the schema's version description. It does not introduce new parameter semantics beyond what the schema provides, 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?

The description clearly states the tool fetches 'elemental content of a journey-scoped notification template', using a specific verb ('Fetch') and resource. It also distinguishes itself from siblings by specifying 'journey-scoped' and version handling, which separates it from generic get_notification_content or get_journey_template. The version parameter is explicitly described, making the tool's function unambiguous.

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 usage guidance for the version parameter ('Pass version=draft for the working draft, or vN for a historical version. Defaults to published.') but does not contrast this tool with related siblings like get_journey_template or get_notification_content. It implies the tool is for journey-scoped content, but does not explicitly state when to choose this over alternatives. Some context is given, but exclusions are missing.

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