divine_get_samvat

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

Annotations already declare the tool read-only, idempotent, non-destructive, and open-world. The description adds that the tool returns current Vikram and Shaka Samvat details for a date/location, but it does not disclose calculation behavior, timezone handling, or edge cases. No contradiction exists.

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 compact sentences with no filler. The operation is front-loaded and the expected return content follows immediately, making it easy to scan and parse.

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 simple, well-annotated tool with an output schema and descriptive input schema, the basic call mechanics are covered. However, the complete absence of usage routing among dozens of sibling tools and the lack of parameter clarification keep it from being fully complete.

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?

The description only vaguely refers to 'date and location' and does not mention any of the required fields (day, month, year, place, lat, lon, tzone) or the optional language parameter. With schema description coverage at 0%, the description fails to compensate, though the schema itself provides useful per-field examples.

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 uses a clear verb and resource: 'Get Samvat (Hindu calendar year) details' for a date and location. It also names the specific outputs (Vikram Samvat and Shaka Samvat year names/numbers), making the tool's function unambiguous even though it does not explicitly distinguish itself from siblings.

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?

There is no guidance about when to use this tool versus the many sibling Samvat/calendar/panchang tools. The description only implies use for Samvat queries and does not state any exclusions, prerequisites, or alternatives.

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