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

Without annotations, the description clarifies that it returns cached sign-level data, not a personalized chart reading, and specifies the output structure. It does not, however, mention any permission, rate limit, or data freshness/determinism concerns beyond 'cached'.

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?

Well-structured with clear sections (WHEN TO USE, WHAT IT DOES, RETURNS, NEXT). Slightly verbose in places but every sentence provides useful guidance or routing information.

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 single-parameter, read-only tool with an output schema, the description covers purpose, usage boundaries, return format, and a next step. The only gap is the lack of parameter naming/format guidance, but that is minor given the simple parameter.

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 description coverage is 0%, so the sole parameter 'sign_name' is undocumented in both schema and description. The description's meaning of 'rashi (Moon sign)' gives some context but does not fully specify accepted sign names or format. Baseline 3 reflects partial semantic support.

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 specific verb and resource ('Get the daily Vedic horoscope (Rashifal) for a zodiac sign') and distinguishes itself from sibling tools by explicitly noting it is sign-based and not personalized. It names daily_horoscope as the alternative for a more detailed, chart-aware reading.

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?

Explicit WHEN TO USE section specifies the condition ('today's prediction for a specific rashi'). It clearly contrasts with daily_horoscope (Pro tier, chart-specific) and even suggests a prerequisite (calculate_birth_chart to find the Moon sign).

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