Varga D12 — Dwadasamsa

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

Annotations already declare readOnlyHint, destructiveHint false, idempotentHint true, and openWorldHint false. The description adds no behavioral context beyond that, such as permissions, side effects, or response behavior, but annotations are sufficient.

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?

Description is extremely concise (one sentence plus non-functional comments). It is front-loaded and clear, but could include a brief note on the chart's purpose or typical use cases without losing conciseness.

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?

Given the simple nature of the tool (single calculation), high schema coverage, and comprehensive annotations, the description adequately states the output (Dwadasamsa chart for parents/ancestral karma). No output schema exists, but the return value is implied by the tool's domain.

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% for all 7 parameters, providing baseline value. The description does not add any parameter-specific semantics beyond what the schema already provides.

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?

Description explicitly states 'Dwadasamsa chart (parents, ancestral karma)', clearly identifying the tool's purpose as computing the Vedic D12 divisional chart focused on parents and ancestral karma. This differentiates it among many sibling varga tools like vedic_varga_D1, D2, etc.

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?

No guidance on when to use this tool versus alternatives. Among many divisional charts (D1, D9, D10, etc.), the description does not specify context, prerequisites, or exclusions. The implied usage from the title is minimal.

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