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 states the output contents (origin tradition, rarity tier, full lore) and language behavior (English + Thai, with 'omit to get both' implied). It does not mention partial-match fallback or error handling, but the schema covers partial matches, so this is acceptable for a read-only lookup tool.

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 two well-structured sentences: the first defines the tool's purpose and output, the second provides concrete use-case triggers. It is front-loaded with the core purpose, includes valuable examples, and contains no filler or redundant statements.

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 sufficiently explains the return values (origin, rarity, lore), language options, and scope (1,044 deities, 9 mythologies). It also gives clear usage triggers. Minor gaps exist around not-found behavior, but the schema's partial-match handling mitigates this. Overall, the description is complete enough for an agent to confidently invoke the tool.

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 description coverage is 100%, so the baseline is 3. The description adds some value by listing example deity names and enumerating the mythologies, which gives context for choosing the deity parameter, but it does not go beyond the schema's own descriptions for 'lang' or 'deity'. It reinforces but does not substantially extend parameter meaning.

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 opens with a specific verb ('Look up an encyclopedic profile') and a precise resource ('1,044 deities across 9 mythologies'), immediately distinguishing it from sibling tools like calculate_cosmic_score or daily_blessing. It also provides concrete deity name examples (Ganesha, Zeus, Odin) and clearly states the returned content (origin, rarity, lore).

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 explicitly lists trigger phrases ('who is X?', 'tell me about the god/goddess X', myth or symbolism, pantheon) making the when-to-use very clear. It does not name alternative tools for similar queries, but the sibling tools are sufficiently distinct that no exclusions are necessary. This meets the 'clear context, no exclusions' level.

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