Name Suggestions

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds real operational context beyond annotations: the HTTP endpoint and a 10-credit Tier 1 cost, which matters for an agent budgeting calls. It does not disclose what the hints look like or how the sign is determined, so it stops short of rich behavioral detail.

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 prose is a single front-loaded sentence with no filler, and the bracketed metadata block is scannable. It is arguably over-compressed for a 13-parameter tool, but nothing is wasted.

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-value explanation is not owed. What is missing is the input-side story: how the sign is derived from the birth-ish data, what `name` does, and whether the caller supplies a business name or only a chart. With 13 parameters at 23% coverage, this is not complete enough for confident invocation.

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 only 23% across 13 parameters, so the description needs to compensate and does not. It echoes the four required fields (already enforced by the schema's required list) but says nothing about the ambiguous optional inputs — notably `name` (presumably the business name whose sign is being read) and `city`, or how `zodiacType`/`houseSystem` change the derived sign. An agent can fill the required fields but cannot reason about the optional ones that likely shape the answer.

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 says what the output contains (syllable structure, palette, semantic field) and ties it to a sign, which is more informative than the bare name 'Name Suggestions'. However, it never states the verb or the business context — the word 'business' appears only in the Group metadata, not in the prose — so an agent must infer from the tool name that this generates business-name ideas. Against dozens of business_* and naming-adjacent siblings (e.g. astroway_pet_best_names), it does not differentiate itself.

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?

No when-to-use guidance and no alternatives named. The tag lines give prerequisites (date, time, latitude, longitude) and a credit cost, but nothing says when an agent should pick this over astroway_reports_business, astroway_business_ideal_industry, or astroway_pet_best_names.

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