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

With no annotations, the description carries the full burden and does real work: it discloses that all five oracles are drawn server-side, that they run in parallel, that interpretation plus synthesis happens server-side, and that there is a hard quota (30 readings per client per day, currently free). It omits latency expectations and whether any auth/account is required for the quota to apply.

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?

Front-loaded with the core action, then usage conditions, then the quota — a sensible order with no padding. Minor redundancy: the 'not for trivial yes/no questions' caution is already repeated verbatim-ish inside the schema's question description.

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?

No output schema exists, and the description does gesture at the return shape ('synthesized into a single unified reading'), plus the free/quota caveat. Missing are rough latency for a five-oracle parallel call and any note about what a failed or partial reading looks like.

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?

Only one parameter and schema coverage is 100%, so the baseline is 3. The description adds value by reinforcing what a well-formed question looks like ('questions of substance', avoid yes/no) and the free-tier constraint that shapes usage, going modestly beyond the schema's own parameter description.

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 ('Consult the Pentamancy Council'), then enumerates exactly what it does — draws five named oracles in parallel and synthesizes one reading. That single/dedicated distinction cleanly separates it from the five consult_* sibling tools that each handle one oracle.

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?

Gives clear selection context ('deep, multi-perspective guidance', 'major decisions, emotional crossroads, spiritual direction') and an explicit exclusion ('Not for trivial yes/no questions'). It never names the individual sibling tools as the lighter-weight alternative, so the routing to consult_tarot/consult_runes etc. is left to inference.

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