Varga D27 — Saptavimsamsa

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 the topics 'strengths, weaknesses, stamina,' which hints at output content but does not disclose any behavioral traits beyond annotations. No contradiction detected.

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 concise, with a clear chart name and topics. It includes practical metadata (group, cost) and an example request body. However, the structure could be improved by front-loading the main purpose and adding a brief sentence on when to use.

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?

The description does not specify the return value or output format. Without an output schema, the agent has no idea what the tool returns (e.g., a chart text, JSON, interpretation). Compared to siblings like vedic_varga_D1, there is no differentiation. The description is incomplete for a tool with 7 parameters and many siblings.

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%, with all 7 parameters described in the input schema. The description does not add parameter-level meaning beyond what the schema provides. The example request body is helpful but does not clarify parameters like houseSystem or city. Baseline score is appropriate.

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 identifies the chart as Saptavimsamsa/Bhamsa chart and mentions strengths, weaknesses, stamina, giving a general sense of purpose. However, it lacks specificity about what the tool actually computes (e.g., a divisional chart for stamina/physical strength) and does not clarify how it differs from other varga tools.

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. It does not mention when D27 is appropriate, nor does it exclude contexts (e.g., male vs female charts, daytime vs nighttime). The sibling list includes many other vargas, but no differentiation is provided.

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