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

Annotations already establish this is not read-only, not idempotent, and not destructive. The description adds useful rank-heightening and default-rank behavior, but does not disclose side effects such as resource/slot consumption or whether the cast triggers rolls or chat output. No contradiction exists.

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?

Three short, purposeful sentences with no filler. The PF2e-only scope is front-loaded, followed by the required item constraint and the key optional parameter behavior.

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 four-parameter tool with a fully-covered schema alert, the description covers system, valid spellId source, rank range/default, and chat projection via schema. It does not explain broader cast consequences, but all invocation-critical information is present.

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 coverage is 100%, so the schema carries most parameter meaning. The description adds the important constraint that spellId must be a spell item on the actorjos, and restates rank behavior already present in the schema, providing only small additional semantic value.

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 uses a specific verb ('Cast') and resource ('spell via its spellcasting entry'), scoped to PF2e and tied to a spell item on an actor. It is clearly distinguishable from sibling item-use/consumable tools even without naming them explicitly.

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 scoping exclusion, and 'spellId must be a "spell" item on the actor (from item-list)' gives concrete sourcing guidance. It does not name alternative sibling tools, but the usage context is clear and actionable.

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