divine_get_pitra_dosha

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint=false. The description adds that it returns remedial measures, which is useful context beyond annotations, but doesn't detail response structure or limitations.

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 at two short paragraphs, front-loading the purpose and effects. It avoids unnecessary detail while being efficient.

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?

With a complex nested schema and no parameter documentation, the description should provide more usage context. It covers the core purpose and output, but given the lack of parameter descriptions, it's not fully complete for correct invocation.

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 has 0% coverage, meaning the description must explain parameters. However, the description says nothing about any of the 12 parameters or the nested structure, leaving the agent to infer how to fill them from the schema definitions.

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 it checks for Pitra Dosha in the birth chart, which is a specific astrological condition. It distinguishes itself from most siblings by focusing on ancestral affliction, although it doesn't explicitly contrast with other dosha tools like manglik or kaal sarpa.

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 when to use it (when needing to assess ancestral karma) but doesn't explicitly state when not to use it or alternatives. Given many dosha-related siblings, explicit guidance would help.

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