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

The description adds useful result semantics by defining isCritical and isFumble, and annotations show this is not read-only/destructive. However, it does not disclose side effects such as whether the roll is posted to chat or whether any actor state changes beyond the roll result, so the description only partially carries the behavioral burden.

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?

Two compact sentences with the system restriction and core action front-loaded; every phrase earns its place and there is no redundant restatement of the title.

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 three-parameter roll tool, the schema covers input details and the description covers outcome labels. An explicit note on where the result appears (chat vs direct return) would make it fully complete, but nothing critical is missing for invoking it correctly.

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 already documents actorId, save, and showInChat. The description reinforces which values save accepts (fortitude/reflex/will) but adds no new meaning beyond the enum and tool scope.

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 strong verb ('Roll'), a specific resource ('Pathfinder 2e saving throw'), and explicitly enumerates the three sub-types (fortitude/reflex/will). The 'PF2e only' opener separates it from dnd5e-roll-save and other system-specific roll tools.

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?

'PF2e only' is an explicit system-level condition and the phrase 'saving throw' tells the agent when to select it over perception, skill, or strike rolls. It does not name a sibling alternative or give an explicit when-not-to-use, so it stops short of a 5.

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