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

The annotations already declare a safe, idempotent, closed-world read, so the safety profile is covered. The description adds genuinely new behavioral context absent from the annotations: cost (10 credits, Tier 1), the endpoint, and the four required inputs. It does not disclose any constraints around the non-required parameters or how the chart engine behaves, but for a compute-style read tool with annotations this is adequate.

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?

One tight lead sentence followed by bracketed metadata (group, endpoint, required, cost) is efficient and front-loaded. Nothing is padded, though the core sentence is arguably too terse to carry the tool's complexity.

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?

For a 15-parameter tool with three enum-bearing options and low schema coverage, the description is thin. An output schema exists so return values need not be explained, but the description gives no guidance on choosing house system, zodiac type, or ayanamsa, nor on the geographic inputs, leaving real gaps for an agent to call it well.

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, and it largely does not. It restates the four required fields (already marked required in the schema) and mentions sun/moon/ASC, but says nothing about city, name, cosmogram, zodiacType, houseSystem, or how the ayanamsa/precision/fields options change the result. The half of the schema that is undocumented remains undocumented here.

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 specific action and output: it treats a proposed founding date as a chart and returns sun/moon/ASC plus a theme. That is a concrete verb+resource, clearly distinct from the interpretive business siblings (founder_personality, leadership_style). It does not, however, name or differentiate itself from the closest siblings like astroway_business_electional_day or astroway_vedic_muhurat_business_start, so an agent must infer the boundary.

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 'proposed founding date' implies the use case — evaluate a candidate date you already have — but the description never states when to prefer this over electional_day (finding a date) or muhurat_business_start. No exclusions or alternatives are given, leaving usage only implied.

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