RWS — Soul + Personality

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds that the tool 'returns' data, which aligns with the read-only nature, but it does not disclose any additional behavioral traits such as whether optional parameters are used or ignored.

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 two sentences plus an example, all front-loaded with the core functionality. No unnecessary words or redundant information.

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?

The tool has no output schema, and the description does not specify the format of the returned data (e.g., card names, numbers, suits). Additionally, the role of optional parameters (latitude, longitude, timezoneOffset) is unclear for a birth-date-based tool. The description should provide more context about the output structure and parameter usage.

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 100%, so the input schema already provides descriptions for all parameters. The description includes an example for the required 'date' parameter but does not add meaning beyond what the schema offers. The optional parameters (latitude, longitude, timezoneOffset) are not explained in the description.

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 clearly states the tool returns a soul card and personality card pair from a birth date. It specifies the verb ('Returns'), the resource ('soul card and personality card pair'), and the input ('birth date'), distinguishing it from similar tools like tarot_rider_waite_birth_card which likely returns a single card.

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 includes an example request showing how to use the tool, but it does not explicitly state when to use this tool versus alternatives (e.g., other tarot tools or zodiac-based tools). No guidance on prerequisites or exclusions is provided.

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