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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description's one addition of substance is the billing metadata ('Cost: 10 credits (Tier 1)', 'Group: Business Astrology'), which is genuinely useful agent-relevant context, but it says nothing about what input data is mandatory or what the response contains.

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 one-line format is front-loaded and wastes no words; the group and cost tags are short and skimmable. It is efficient rather than verbose, but its brevity stems from under-specification rather than tight writing.

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, 4-required computation tool in a dense sibling cluster, the description omits everything an agent needs beyond the annotation-covered safety profile: required inputs, output shape (though an output schema exists, so return values need not be explained), and discrimination from adjacent business tools. Only the credit cost is additive.

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 description coverage is only 33% across 15 parameters, so the description is expected to compensate and does not. The four required parameters (date, time, latitude, longitude) — the core birth-data triple an agent must collect — are never mentioned, and no guidance is given on defaults or the sidereal/tropical choice.

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 phrase 'Concise leadership archetype + key strengths' describes the returned artifact rather than an action, so the agent knows what output to expect but not what operation runs. It gives no differentiation from near siblings like astroway_business_founder_personality, astroway_business_marketing_style, or astroway_business_risk_profile, which all produce business-oriented archetypes.

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 at all: no indication of the prerequisite birth data, no distinction from the other business_* archetype tools, and no note on whether it should be called alongside a founding chart. The agent must infer placement from the name alone.

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