get_yogas

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

No annotations provided, so description must carry full behavioral burden. It states the tool returns yoga name, planets involved, and interpretation, but doesn't mention computational complexity, birth time precision requirements, or whether it handles edge cases like missing planetary data. Contradicts nothing since annotations are absent.

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?

Two sentences, front-loaded with purpose and list of yoga types. Efficient and scannable.

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, so description should clarify return structure. It mentions 'yoga name, planets involved, and interpretation' but lacks detail like data format or pagination. Adequate for a tool with 5 simple parameters but could be more thorough.

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 baseline is 3. Description does not add parameter-specific meaning beyond schema descriptions (e.g., format examples). It mentions inputs implicitly (birth chart) but doesn't explain how parameters affect yoga detection.

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 the tool detects and lists Yogas in a birth chart, specifying types like Raj Yogas, Dhana Yogas, and Panch Mahapurusha Yogas. It distinguishes from siblings like 'check_mangal_dosha' which are specific defect checks, but doesn't differentiate from other chart interpretation tools.

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?

No guidance on when to use this tool vs alternatives. Siblings include various dosha checks and dashas, but the description doesn't clarify when yoga analysis is preferred over other astrological components.

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