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

Annotations only cover safety flags (destructive=false, openWorld=false); the description adds real behavioral context: a short screenshot-shareable output, BSV as the translation, movement tagging, and explicit style constraints ('no anthropomorphism, no AI companion framing'). It does not explain the non-idempotent/readOnlyHint=false semantics, but that is a minor gap.

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 dense sentences, front-loaded with the core action and then the output contract and constraints. Slightly overloaded with the full nine-item movement list, which the schema already carries, but no sentence is wasted.

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?

With no output schema, the description does the work of describing the return value (short, shareable, Scripture-anchored, movement-tagged) and the voice constraints. For a 2-parameter generation tool this is nearly complete; only the sibling-routing and non-idempotency nuances are unaddressed.

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 both parameters are already documented, including the enum. The description reinforces the nine-movement vocabulary and notes inference when movement is absent, matching the schema's own statement that the server infers, but adds no format or syntax beyond it. 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?

States a specific verb and resource: 'Generate Christian encouragement in the Doxa voice for the situation a user describes,' plus the anchoring source (Berean Standard Bible) and the output shape. It is clearly distinct from a raw scripture lookup, but it never names its siblings doxa_scripture or doxa_way_movement, so the differentiation is left implicit.

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?

Usage is implied by 'for the situation a user describes,' which tells the agent this is the situation-driven tool, but there is no explicit when-to-use versus doxa_scripture or doxa_way_movement, and no stated prerequisites (e.g., when a movement should be supplied vs. inferred).

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