Yogas — Jaimini Daridra yoga

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

Annotations already declare readOnlyHint, idempotent, non-destructive. Description adds that it returns a 'poverty/struggle flag' and suggests remedies, providing behavioral context beyond annotations.

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?

Short and includes example request and group tag. However, the description could be more informative without being verbose; it lacks parameter details.

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 11 parameters, no output schema, and no parameter descriptions, the description is incomplete. It does not explain the response format beyond a vague flag and remedies, nor how parameters affect the calculation.

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 has 11 parameters with 0% description coverage. The description does not explain any parameter meaning, only shows an example request. Fails to compensate for low coverage.

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?

Clearly states the tool checks Jaimini Daridra yoga (AK+AmK in dusthanas) as a poverty/struggle flag with remedies. Distinguishes itself from many sibling Jaimini yoga tools by naming a specific yoga type.

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?

Implies usage for checking this specific yoga condition, but no explicit when-to-use or when-not vs siblings like dhana, raja, etc. Missing guidance on prerequisites or context.

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