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

With no annotations, the description carries the behavioral burden. It clearly discloses that no interpretation is provided ('ТОЛКОВАНИЯ ЗДЕСЬ НЕТ'), that the agent must make conclusions from the data, and that free-text questions are rejected. This is strong transparency for a read-only calculation tool, though it omits any mention of error handling or prerequisites such as chart availability.

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 compact and front-loaded: purpose and topic list first, then the output contents, then behavioral warnings. Each sentence carries distinct value and nothing is redundant. The opening phrase is slightly awkward but not bloated.

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 that an output schema exists, the description does not need to explain return values in detail; it covers the critical behavioral context and the main invocation constraint. It is sufficiently complete for an agent to call the tool correctly, though explicit selection criteria relative to sibling tools would improve it further.

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 description adds meaningful semantics to the topic parameter: it names the five valid topics and explicitly instructs that the agent must name the topic and cannot submit free text. However, schema coverage is 0%, and the description does not compensate for the remaining parameters (date, time, place, chart_id, geonameid, lang, ayanamsa), leaving much of their meaning to be inferred from the schema's enums and defaults.

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 states a concrete action ('Отдаёт') and enumerates exactly what is returned: houses, signs, rulers, planets, varga, and current period. It also pins down the allowed topic set. However, it does not explicitly differentiate this tool from sibling tools like natal_chart or dasha_timeline, so it stops short of a 5.

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 phrase 'одним вызовом вместо пяти' implies this tool is an aggregate for a set of related astrological lookups, and the warning instructs the agent to supply the topic rather than free text. There is no explicit statement of when to prefer this tool over alternatives or which sibling tools it replaces, so usage guidance remains largely implicit.

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