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

With no annotations, the description fully explains behavioral traits: returns full timeline with UTC start/end, optionally identifies active period, requires lat/lon for sect, and is time-only calculation.

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 a single paragraph that efficiently explains the core concept, required inputs, and output. While dense, every sentence adds value.

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 complexity of Firdaria and no output schema, the description adequately explains the structure (nine major periods, seven planets, nodes, sub-periods) and what the tool returns.

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%, but the description adds meaning: explains why lat+lon are needed (sect), clarifies date format and UTC requirement, and specifies target_date is optional.

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 specifies the tool calculates Firdaria (Persian/medieval planetary time-lord periods) and returns a timeline of major and sub-periods. It clearly distinguishes from sibling tools like dasha by name and context.

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?

It states sect is derived from the birth chart, requiring lat+lon, and that the tool performs 'pure time arithmetic, no zodiac.' It implies use for Firdaria queries but does not explicitly exclude alternatives.

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