vedika_predictions

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

With no annotations, the description carries the behavioral burden and does well by disclosing caching and billing: the first call per sign per day is charged and subsequent same sign+day calls are free. It also gives the cost range. It does not describe output format or error behavior.

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 front-loaded with the core action and then packs period options, input modes, caching, sign-language support, and pricing into a compact set of sentences. Every sentence adds actionable information with no wasted prose.

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?

For a six-parameter prediction tool with no output schema, the description covers invocation, period choices, input modes, caching, and pricing well. It is slightly incomplete because it does not explain the return shape and does not route the agent away from overlapping sibling astrology tools.

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, but the description adds useful conditional semantics beyond the schema: either rashi or datetime is needed, and sign names are accepted in English or Hindi. It does not fully document the datetime companion fields, which the schema handles.

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 states a clear verb and resource: get Vedic astrology predictions for a zodiac sign or from birth details, across specified periods. It is specific enough for an agent to know what the tool returns, but it does not explicitly distinguish itself from nearby siblings such as vedika_horoscope or vedika_daily_bundle.

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 explains the two input modes: provide rashi for sign-based predictions, or provide birth datetime to derive the Moon sign. However, it gives no explicit when-to-use guidance versus sibling prediction or horoscope tools, and no when-not-to-use conditions.

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