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

Annotations already 'offer' read-only and non-destructive safety, so the description carries less burden. It goes beyond that by naming the exact return pieces (compound/root number, planetary ruler, rating, favored industries, Cheiro status) and adding a clear caveat: 'This is a positioning guidance layered over the fundamentals... not a guarantee.' This is honest and useful for expectation-setting.

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 compact and front-loaded: it starges the purpose, enumerates the key outputs, highlights the most relevant numbers, and gives use cases and a caveat. Every sentence contributes to understanding the tool. The phrase 'the system practitioners use for trade names' adds tone but is not essential; still, the overall structure is efficient.

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 no output schema, the description does the important work of listing the expected return fields (compound and root number, planetary ruler, rating, industries, Cheiro fortune) and giving interpretation context for critical numbers like 4 and 8. It's enough for an agent to know what to expect from a business-name check. It doesn't document the exact JSON shape, but that is a minor gap when the semantic results are clearly named.

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 schema covers all three parameters with descriptions, so the baseline is 3. The natural description reinforces the 'name' semantics by calling it a business or brand name, but it adds no extra detail about 'lang' or 'compact' beyond what the schema already provides. No negative signals either; the baseline is acceptable.

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 starts with a definite verb and resource: 'Analyze a business or brand name with Chaldean numerology.' It clearly distinguishes itself from sibling personal-number tools by emphasizing business names and trade names, and enumerates specific outputs like the compound and root number and planetary ruler. This is not tautological and leaves no ambiguity about what the tool selects with exceptional clarity.

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?

'Use it to vet a company name, compare brand options, or guide a naming decision' gives a crystal-clear purpose for use. It doesn't explicitly mention when not to use this tool or name alternative tools, but the context signals and the specialized business-name scope make the choice almost self-evident among all sibling numerology tools. A small explicit 'not for personal name readings' would push this to 5.

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