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

While annotations already declare readOnlyHint and destructiveHint, the description adds meaningful behavioral context: it requires no API key, is deterministic (same date → same reading), and explicitly states it does not pray on the member's behalf or claim divine knowledge, pointing to pastoral care. This goes beyond the annotations and clarifies what the tool will and will not do.

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 longer than average but every sentence serves a purpose, and the core purpose is front-loaded. The 'two things this is not' section is clearly structured and high-value, preventing common misuses. It could be trimmed slightly, but the density of useful information justifies the length.

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 fully explains the return contents and behavior, including the absence of auth, deterministic outputs, and the intended pastoral posture. For a read-only devotional builder, nothing crucial is missing; an agent can call it correctly and set expectations.

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 already explains both parameters. The description mentions the season-aware selection but does not explicitly link the 'reference' parameter to overriding the seasonal choice; that is only in the schema. It adds marginal value by confirming the devotional's seasonal nature, but no extra parameter-level detail 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?

The description states a specific verb ('build'), a resource ('a season-aware daily devotional'), and enumerates the exact outputs (liturgical season/colour, KJV passage, three reflection questions, prayer prompt). It also explicitly distinguishes itself from the lectionary and from homilies, which differentiates it from siblings like get_lectionary and get_sermon.

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 clearly states when not to use this tool (it is not the lectionary, not a homily/spiritual direction) and gives the context that it is a study aid. It does not explicitly name alternative tools but the exclusions effectively guide an agent away from misapplying it. The determinism note ('same date always returns the same reading') adds a relevant usage condition.

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