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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world computation, so safety behavior is covered. The description adds genuinely useful operational context not present in annotations: the credit cost and tier. It says nothing, however, about the formula's effect on output or any input constraints beyond what the schema carries.

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?

It is a single tight sentence plus two bracketed tags, front-loading the chart identity and its meaning with zero filler. It is arguably a touch terse for a tool with 15 parameters, but every element present earns its place.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. What is missing is selection guidance within the dense varga family and any acknowledgement of the required birth-data inputs, leaving the definition adequate but with clear gaps for a Tier 2 tool.

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?

With 15 parameters and only 33% schema description coverage, the description is expected to compensate for the undocumented inputs but adds nothing at all about date, time, latitude/longitude, ayanamsa, zodiacType, or houseSystem. An agent gets no help here beyond the raw schema.

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 names the specific artifact (Trimsamsa / D30 divisional chart) and its astrological domain (misfortunes, evils), and pins the computation method (Parashara unequal-segments formula). Combined with the name suffix d30 and the title, an agent can distinguish it from the other varga siblings, though the description itself never contrasts them explicitly.

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 on when to request a D30 chart versus the many sibling vargas (d9, d10, d60, etc.), nor any stated prerequisites. The '[Group: Vedic]' and '[Cost: 20 credits (Tier 2)]' tags are catalog metadata, not usage direction, so the agent must infer selection purely from the chart name.

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