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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds no behavioral context of its own: nothing about determinism, latency, required birth data, or what 'founder profile' means operationally. It neither contradicts nor enriches the annotations.

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 front-loaded sentence, with the group and pricing metadata clearly segregated in bracketed lines. Nothing is padded, though the brevity is partly under-specification rather than efficiency.

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, but for a 15-parameter computation tool with low schema coverage and no usage or behavioral notes, the definition leaves the agent without enough to invoke it confidently. It should at minimum state what inputs constitute the 'founder profile' and how the result is selected.

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?

Only 33% of the 15 parameters are described in the schema, and the description compensates for none of the gap. The phrase 'this founder profile' faintly implies natal inputs (date, time, latitude, longitude), but there is no explanation of the ayanamsa, zodiacType, houseSystem, fields, or precision parameters that materially change the output.

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 a resource (industries suited to a founder profile) but supplies no verb, so it is unclear whether the tool computes, ranks, or retrieves them. It is distinguishable in topic from siblings like astroway_business_leadership_style or astroway_business_founder_personality, but the phrasing is a bare noun phrase rather than a stated action.

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 when-to-use guidance, no prerequisite conditions (e.g., that a birth chart profile must be supplied), and no mention of adjacent business tools such as astroway_business_founding_chart or astroway_business_expansion_timing that an agent might confuse it with. The agent must infer everything from the name.

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