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

Annotations already cover safety (readOnlyHint, destructiveHint=false, idempotentHint, openWorldHint=false), so the bar is lower. The description adds valuable non-obvious context: a credit cost model including that only successful calls are charged and that a sandbox key returns a fixed sample, plus determinism. This is useful operational detail beyond the structured fields.

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 short, line-structured, and front-loads the resource before cost and determinism notes. Each line (cost, determinism, example) earns its place, though 'Deterministic' partially overlaps the idempotentHint annotation.

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 tool with full schema coverage, an output schema, and safety annotations, the description supplies the operational facts an agent needs (cost, determinism, sample invocation). Return values need not be explained given the output schema, though the absence of any when-to-use context is a remaining 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?

Schema description coverage is 100% and the nested birthData object is fully documented, so the baseline is 3. The description goes further by supplying a complete, valid example argument object, which concretely demonstrates the required nesting, field names, and format needed to invoke the tool correctly.

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 opens with 'Vimśottarī daśā timeline,' which is a verbatim restatement of the title rather than a statement of what the tool does. It supplies no verb (compute/return/list) and no differentiation from siblings like get_chart, get_forecast, or resolve_timing. This is a tautology of the name/title.

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 indication of when to use this tool versus alternatives such as get_chart, resolve_timing, or get_forecast, which all appear to operate over the same birth data. No prerequisites or exclusions are stated. The agent must infer the tool's role entirely from the name.

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