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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral context in the form of cost ('5 credits, Tier ½'), which is quota-relevant information not present in any structured field, but says nothing about output shape, caching, or computation requirements.

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?

Extremely compact and front-loaded: the domain statement comes first, followed by grouped metadata tags. Nothing is padded, though the brevity borders on under-specification rather than true economy.

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 an output schema present and annotations covering the safety profile, the description need not explain return values. But for a chart-computation tool it omits what the result represents and that it derives from birth data, leaving the agent to infer the action from the title alone.

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 67% and the description adds no parameter detail at all — no clarification of the required date, the time field, or how timezone interacts with charts. The rich schema prose for timezone/fields/precision carries the load, so a baseline 3 is warranted rather than a penalty.

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 'Profession, status, official position' labels the semantic domain of the Career Palace and thereby distinguishes it from sibling palaces like wealth or spouse. However, it never states a verb — it does not say whether the tool computes the palace, returns its stars, or produces an interpretation. An agent knows the topic but not the action.

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 prerequisites (e.g. that birth date/time is needed), and no routing to alternatives. The only routing signal is the '[Group: Zi Wei Dou Shu]' tag, which is supplementary metadata rather than usage instruction.

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