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

The readOnlyHint and destructiveHint annotations already establish the tool is a safe read operation. The description adds useful context about the reduction process and return value composition (challenges, resolution strategies). It does not cover edge cases like what happens when no karmic debt number is present, but with annotations present, this is an acceptable disclosure level.

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 core functional statement is clear and front-loaded, but the final marketing sentence listing spiritual growth apps and past life services adds little value for an AI agent selecting the tool. The description is reasonably sized but could be more tightly focused without this filler.

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 tool has no output schema, the description helpfully mentions the return items: debt descriptions, challenges, and resolution guidance. It also indicates the calculations covered and makes reasonable assumptions to complete. Remaining details like default behavior when multiple karmic debts are found, are not essential for invocation given the schema and annotations.

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 schema covers all 6 parameters with detailed descriptions (e.g., month, day, year for Life Path; fullName for other calculations). The description adds no parameter-level details beyond what the schema already communicates, so the baseline of 3 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 clearly states the tool checks for Karmic Debt numbers (13, 14, 16, 19) across specific numerology calculations, using a specific methodology (Pythagorean numerology). It is clear about the subject matter and scope, but it does not explicitly distinguish itself from its closest siblings like post_numerology_karmic_lessons, so it stops short of full differentiation.

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?

The description provides clear context for when to use the tool, including applicable use cases ('spiritual growth apps, karmic astrology platforms') and the specific calculations it applies to. However, it lacks explicit exclusions or guidance about when to use an alternative tool, such as post_numerology_karmic_lessons.

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