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 does transparently state that a random ghazal is drawn, that interpretation is delivered in a Sufi scholar voice, and that there is a cost of $0.10 per call. However, it does not describe the output format, reliability, or any limitations such as the interpretive nature being subjective.

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 concise and well-structured, front-loading the core practice and behavior before adding usage guidance and cost. Every sentence contributes useful information without redundancy.

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 single-parameter tool with no output schema, the description covers the core purpose, behavior, use cases, and cost. It is slightly incomplete in that it does not describe the expected return structure, but the mention of 'draws a random ghazal and interprets it' gives enough of an outline for an agent to understand the result.

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 documents the only parameter with 100% coverage, so the baseline is 3. The description adds meaningful semantic guidance by suggesting the types of questions that are suitable, which helps the agent formulate a better 'question' value beyond the schema's generic definition.

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 clearly states a specific verb and resource: consulting Fal-e Hafez via a random ghazal from the Divan. It also differentiates the tool from its siblings by emphasizing Persian poetry and themes of love, hope, and longing.

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?

It gives explicit guidance on when to use the tool, namely for 'questions of the heart, longing, love, hope, and the soul's quiet questions.' It does not explicitly mention when not to use it or name alternatives, though the thematic framing effectively implies a distinction from the other oracle tools.

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