Personality (pythagorean)

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered; the description adds genuinely new operational context: a POST endpoint, required inputs, and a 10-credit Tier 1 cost that an agent should weigh before calling. It does not describe the failure mode or what happens with non-alphabetic names, so it stops short of full disclosure.

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 core sentence is tight and front-loaded with the derivation rule. The bracketed metadata block is mostly useful (endpoint, cost) but '[Required: name, date]' simply restates the schema's required array, which is minor redundancy rather than waste.

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 only two parameters, an output schema and full annotations, the definition needs to explain the one non-obvious input, `date`, and it does not. Everything else an agent needs to invoke the tool is present, so this is adequate but leaves a real interpretive hole.

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 0%, so the description must carry the load. It clarifies `name` as the full birth name (important, since consonants of a nickname would give a different result) but leaves `date` completely unexplained — an agent cannot tell whether it is the birth date, today's date, or why a consonant-based number needs a date at all.

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 (Calculate), a specific resource (the Personality number), and the exact derivation rule (consonants of the full birth name) plus the system (Pythagorean). That combination lets an agent distinguish it from the Chaldean, Kabbalistic and Vedic personality siblings without opening any 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 description implies when the tool applies (you want the Pythagorean Personality number) but never says when to pick Pythagorean over the Chaldean/Vedic/Kabbalistic variants or over soul_urge/expression, and gives no prerequisites. Usage has to be inferred from the system label rather than stated.

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