Yogas — Gajakesari

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

Annotations already indicate readOnlyHint=true and idempotentHint=true. The description adds behavioral context by explaining the yoga condition and including cost/group info, but does not specify what the tool returns (e.g., boolean or details) or how it handles inputs.

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 and front-loaded with the core condition. It includes group and cost info in brackets and an example. However, the example could be more helpful if it explained parameters.

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 is provided, and the description does not mention what the tool returns (e.g., a boolean, a list, or details). Given the 11 parameters and specific yoga, this is a significant gap.

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?

With 0% schema description coverage, the description fails to compensate. It only provides an example request body without explaining any parameter's meaning, leaving the 11 parameters largely cryptic.

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 defines the yoga condition precisely: 'Jupiter in a kendra (1, 4, 7, 10) from Moon.' It names the specific yoga and notes its classical significance, clearly distinguishing it from sibling yoga 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?

The description implies usage when checking for Gajakesari Yoga but provides no explicit guidance on when to use versus alternatives, nor any when-not-to-use criteria.

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