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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly communicates what the tool produces (short, screenshot-shareable response), the source content (Berean Standard Bible), the tagging scheme (nine movements), and important constraints (no anthropomorphism, no AI companion framing). This goes beyond the schema to explain the tool's style and boundaries, which is highly valuable for correct invocation.

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 three sentences long, front-loaded with the primary action, and every phrase earns its place. It packs in the purpose, output format, scriptural basis, tagging scheme, and style exclusions without redundancy. This is a model of concise, information-dense tool documentation.

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?

Despite lacking an output schema and annotations, the description provides sufficient context for correct use: what input is needed (situation), what output to expect (short, screenshot-shareable, Scripture-anchored), and what constraints apply (no anthropomorphism). The two-parameter schema is simple, and the description fills the gaps well, leaving little ambiguity for the agent.

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?

The schema already covers both parameters at 100% coverage, so the baseline is 3. The description adds meaning by clarifying that the output is tagged to one of the nine movements, which reinforces the purpose of the 'movement' parameter. It also implies that 'situation' is the core input for generating the encouragement. The added context is helpful but not extensive; still, it slightly exceeds the schema-only baseline.

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 begins with the specific verb 'Generate' and identifies the exact resource: Christian encouragement in the Doxa voice, tailored to the user's situation. It further distinguishes itself from sibling tools by specifying the Scripture anchor (BSB) and the nine-movement tagging, making it clear this is the encouragement generator rather than a Scripture lookup or movement explainer.

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 states the intended use case ('for the situation a user describes') and the output characteristics (screenshot-shareable, Scripture-anchored). It does not explicitly name alternative tools or exclusion criteria, but the context is clear enough for an agent to infer when to use this tool. The sibling names independently hint at alternatives, but the description itself could be more explicit.

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