vedika_crystals_recommend

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

With no annotations, the description carries the full burden and does substantial work: it discloses provenance (Garuda Purana, BPHS), describes what the response contains, and — unusually valuable — states the per-call cost of $0.012. It stops short of covering error behavior or what happens when zero parameters are passed on a tool with no required params.

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?

Four sentences, front-loaded with purpose then output then provenance then pricing. No filler; every sentence contributes information an agent would otherwise have to infer.

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 compensates by enumerating the returned fields (properties, chakra, cleansing method, usage). The remaining gap is behavioral — no guidance on the zero-required-parameter case or on combining filters.

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 coverage is 100%, so the baseline is 3; the description adds marginal meaning by clarifying that signs may be Vedic or Western and that the planet parameter returns BPHS primary and secondary gemstones to strengthen that planet. That goes slightly beyond the schema's per-parameter descriptions.

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 pair ('Get crystal and gemstone recommendations') with three explicit selection axes: sign, planet, need. It also names the output contents (properties, chakra, cleansing method, usage), so an agent can distinguish it from siblings like vedika_lalkitab_remedies or vedika_spiritual_mantra without opening the schema.

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 implies the three ways to invoke the tool ('based on zodiac sign, ruling planet, or specific need') but never states when to prefer one over another, whether they can be combined, or what happens if none is supplied. Usage is inferable but not guided.

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