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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context by detailing the return payload ('RETURNS Francis Bacon cards, Latin cipher suite, periodic{} + periodic_set{}, numerology...') and a 'Free-text input guard'. This goes beyond the annotations without contradicting them.

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 densely packed but well-structured with clear USE/NOT/RETURNS sections. Every sentence provides distinct value: usage scope, exclusions with alternatives, and output contents. No fluff or repetition, and the structure makes it easy to scan.

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?

Given the single parameter and no output schema, the description fully covers input scope, exclusions, return payload, and a guard. It provides all necessary information for an agent to select and invoke the tool correctly, including explicit sibling alternatives. No critical gaps remain.

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?

The input schema fully describes the single parameter 'full_name' with a clear description and 100% schema description coverage. The description only restates the parameter's purpose ('person or word name text only') without adding new semantic details. Baseline of 3 is appropriate since the schema carries the load.

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 explicitly states 'USE for person or word name text only' and clearly identifies what the tool does: gematria to cosmic cards plus numerology. It also distinguishes itself from siblings by listing exclusions and alternatives ('NOT for any date questions... → get_date; two people → get_compatibility'). This is a specific verb+resource with clear differentiation.

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?

It provides explicit when-to-use ('USE for person or word name text only') and when-not-to-use with named alternatives ('NOT for any date questions... → get_date; two people → get_compatibility'). This directly guides the agent to select the correct tool and avoids misuse.

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