get_deity_lore

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is fully covered. The description adds case-insensitivity and partial-match-fallback behavior, which is useful beyond annotations, but does not describe output structure, rate limits, or error behavior.

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 capability and scope, then usage triggers, then a citation note. Slightly verbose in the mythology enumeration but every element carries information for the caller.

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 states what is returned (origin tradition, rarity tier, full lore in EN+TH). It also discloses partial-match fallback behavior. Missing only edge-case/empty-result guidance, which would push it to 5.

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 schema already documents both parameters including the lang enum. The description adds no parameter syntax or format details beyond the schema. Baseline 3 is appropriate.

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 ('look up') and resource ('encyclopedic profile of any of 1,044 deities across 9 mythologies'), names the categories covered, and gives concrete examples. Clearly distinguishable from siblings like calculate_cosmic_score or daily_blessing.

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?

Explicitly says 'Use whenever a user asks who is X?, tell me about the god/goddess X, the myth or symbolism of a deity, or about a pantheon.' This is strong trigger-language guidance. The tool is the only deity-lookup sibling, so no alternative routing is needed, but no exclusions are given either.

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