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

The annotations already declare readOnlyHint=true, so the read-only nature is covered by structured data. The description adds 'version history' context but does not disclose additional behaviors such as pagination semantics, ordering, or whether versions include metadata. It does not contradict the annotations, and the list operation is consistent with readOnlyHint, but no extra behavioral detail is provided beyond the schema fields.

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, direct sentence with no filler or redundant phrasing. It is appropriately sized for a straightforward list operation and front-loads the core purpose. Every word contributes to clarity.

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 simple read-only list tool with full schema parameter documentation and a readOnlyHint annotation, the description is nearly complete. The lack of an output schema means the description could theoretically explain return shape, but 'version history' is sufficiently informative for an agent. Minor gaps like ordering or version metadata are not critical given the simplicity.

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 the schema fully documents notification_id, limit, and cursor. The description adds no parameter-level meaning beyond what the schema already provides, which matches the baseline of 3. The tool is simple enough that this is acceptable.

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 states a specific verb and resource: 'List version history for a notification template.' This clearly identifies both the action and the object, distinguishing it from sibling tools like list_notifications or list_journey_versions. The resource type is explicit enough for an agent to select this tool without ambiguity.

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 implies the use case (retrieving version history of a notification template) but does not explicitly state when to prefer this over alternatives or when not to use it. There is no mention of related tools such as get_notification or get_notification_draft_content, leaving the agent to infer the boundary from the name and description.

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