Destiny Palace (Ming)

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

The annotations already declare readOnlyHint=true, idempotentHint=true, etc., providing a clear safety profile. The description adds an example request body but no additional behavioral context (e.g., what data is returned, side effects). It does not contradict annotations.

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 short and front-loaded with key phrases. It includes a group label and an example request, both useful. Every sentence contributes value without excess.

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 lacks information about return values or output format, which is critical given no output schema. It does not explain when to use optional parameters (latitude, longitude, timezoneOffset) or what the response contains. For a complex astrology tool, this is insufficient.

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 coverage is 100%, so the baseline is 3. The description provides an example request body showing the required date parameter, but adds no further meaning beyond what the schema already describes for each parameter.

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 'Life path, character, soul mission' gives a vague sense of the tool's purpose but does not clearly state that it provides an interpretation of the Destiny Palace in Zi Wei Dou Shu. It lacks specificity and does not distinguish from sibling tools like ziwei_palace_career or ziwei_main_stars.

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?

There is no guidance on when to use this tool vs alternatives, such as other ziwei palace tools. The description does not mention use cases, prerequisites, or situations where this tool is preferred.

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