doxa_encourage

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

With no annotations provided, the description fully discloses key behaviors: output is short and screenshot-shareable, anchored in Scripture (BSB), tagged to a movement, and explicitly states no anthropomorphism or AI companion framing. No contradictions with annotations.

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 sentences efficiently convey all necessary information. Purpose is front-loaded, and every word earns its place without redundancy or 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?

For a simple generation tool with 2 parameters and no output schema, the description provides sufficient context: expected input, output format, constraints, and classification. Minor lack of information on error handling or availability, but adequate for agent invocation.

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%, but the description adds significant value: clarifies the movement parameter as optional with server inference, and specifies situation max length and recommended brevity (1-3 sentences). This enhances agent understanding beyond the schema.

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?

Clearly states the tool generates Christian encouragement in the Doxa voice for a user-described situation, specifying output format (short, screenshot-shareable), source (Scripture, BSB), and classification (one of nine movements). Distinguishes from siblings by focusing on encouragement generation rather than scripture lookup or journey map information.

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?

Implies usage is for user-described situations needing encouragement. While it doesn't explicitly state when not to use or name alternatives, the context is clear and the tool's purpose is well-defined.

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