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

With no annotations, the description carries the full burden and does well: it discloses that a ghazal is drawn at random, that output is styled as a Sufi scholar's interpretation, and that there is a hard rate limit (30 readings per client per day) plus a free/pricing status. Auth requirements and precise response structure are not addressed, but the operational traits an agent needs are largely present.

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 what the practice is and what the tool returns, followed by domain guidance and operational constraints. The 'oldest and most-used oracle on SpiritWave Labs' sentence is mild promotional filler, but the rate-limit sentence earns its place.

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, so the description correctly explains what comes back (an interpreted ghazal in a scholar's voice). For a one-parameter divination tool with no annotations, it covers identity, return nature, and rate limits adequately; only auth and any error behavior are unstated.

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?

There is a single parameter, and schema description coverage is 100% ('The question to consult Hafez about' with minLength/maxLength constraints). The description adds no syntax, tone, or formatting guidance for the question beyond what the schema already states, so the 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 (consult) and resource (Fal-e Hafez / a random ghazal from the Divan) plus what it produces (an interpretation in the voice of a Sufi scholar). It also scopes the domain (questions of the heart, longing, love). It never names a sibling oracle, so the agent must infer differentiation from the thematic domain alone.

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?

"Best for questions of the heart, longing, love, hope, and the soul's quiet questions" gives clear thematic context for when to choose this tool over a generic consultation. However, no explicit when-not condition and no sibling (consult_tarot, consult_iching, etc.) is named as an alternative, so routing still requires inference.

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