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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered by structured data. The description adds genuinely useful non-schema context: it belongs to the Zi Wei Dou Shu group and costs 5 credits (Tier 1/2), which matters for budgeting. It omits, however, that a birth date is required and that accuracy depends on birth time/timezone.

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?

It is short and front-loaded with the thematic line first, followed by structured group/cost tags. There is no filler, but the brevity reflects missing content rather than disciplined compression.

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?

For a chart-derivation tool with six parameters and an existing output schema, the return value need not be explained, but the description still leaves out the essential fact that it requires birth date/time and how it relates to the other ziwei palace tools. An agent would have to guess its place in the Zi Wei workflow.

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 description says nothing about any of the six parameters. With schema description coverage at 67%, the two undescribed parameters (date, time) fall entirely on the schema's patterns, and the description does nothing to compensate for the gap.

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 restates the title thematically ('Destiny Palace' -> 'Life path, character, soul mission') without stating the operation: computing the Ming/Destiny palace of a Zi Wei Dou Shu chart from birth data. It never differentiates itself from the eight sibling palace tools (career, wealth, spouse, health, etc.), so an agent cannot tell which palace it returns from the text alone.

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 when-to-use guidance, no statement of required inputs (birth date, ideally time), and no mention of the sibling palace tools as alternatives. The only context offered is group and billing metadata, which does not help select between tools.

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