cn402_folk_lucky-number

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

No annotations are provided, so the description carries full responsibility. It explains the computational method (BaZi day master Five Elements) and includes pricing information (auto-paid in USDC), which is important behavioral context. It does not indicate any destructive side effects, which is appropriate for a read-only computation.

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 verbose, with multiple synonyms for 'personal lucky numbers' listed at the beginning. This repetition wastes space and is not concise. The key information (computation method and use case) is present but could be conveyed in one or two sentences.

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 description explains the tool's purpose and method but fails to describe the output format (e.g., list of numbers, count). Since there is no output schema, the description should clarify what the agent can expect as a return value. The inclusion of pricing is extra but not essential.

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 only parameter, 'birth', is already documented in the input schema with format YYYY-MM-DD. The description does not add new meaning beyond stating that it uses the birth date for computation. Schema coverage is 100%, so a baseline of 3 is appropriate.

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 computes personal lucky numbers from birth date using BaZi day master Five Elements. It is specific to lucky numbers, differentiating it from other bazi or folk tools like cn402_bazi_wuxing or cn402_folk_lucky-color. However, the title is null and the description includes many synonyms that are unnecessary.

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 mentions the tool is for AI agents handling lottery suggestions and lucky number recommendations, providing some context. However, it does not explicitly state when to use this tool versus alternatives or when not to use it. No exclusions or alternative tools are mentioned.

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