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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds information the annotations cannot: a billing cost of 10 credits (Tier 1), which is material for an agent deciding whether to invoke. It adds nothing about computation limits or error behavior, but with an output schema present that is an acceptable gap.

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?

Two clauses plus two bracketed metadata tags, no filler. The operative sentence comes first and the cost/group tags follow, so the essential meaning is front-loaded.

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?

With annotations covering the safety profile and an output schema handling return values, the description only needs to establish purpose, input identity and cost — all present. The gap is the undocumented required date format and the absence of any usage/routing guidance among the many numerology siblings.

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 50%: `name` and `date` are undocumented in the schema. The description partially compensates by specifying that the name must be the full birth name (consonants are extracted from it), which is genuinely useful, but it says nothing about the required YYYY-MM-DD date format or the 2-120 char name bounds.

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?

States a specific verb+resource (calculate the Personality number) and names the exact input derivation (consonants of the full birth name) plus the system (Pythagorean). Against a sibling list containing chaldean, kabbalistic, vedic and numks personality variants, the system label alone lets an agent disambiguate without opening a schema.

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 group tag '[Group: Numerology: Pythagorean]' implies the context in which this is the right choice, and the system name separates it from the other personality tools. But there is no explicit when-to-use statement, no mention of prerequisites, and no guidance on choosing it over e.g. astroway_numerology_pythagorean_soul_urge or the chaldean personality sibling.

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