Property Palace (Tianzhai)

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating safe reads. The description adds no behavioral context (e.g., authentication needs, rate limits, or result format). It neither contradicts annotations nor adds meaningful value beyond them.

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 very short and includes a group tag and example. It is front-loaded with key terms. However, it lacks structured sections or formatting that could aid readability for an AI agent.

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 is part of a complex system (Zi Wei Dou Shu) and has four parameters, but the description does not explain return values, required inputs beyond date, or how to interpret results. No output schema exists, so the description should compensate but does not.

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% but parameter descriptions are minimal (e.g., 'Date YYYY-MM-DD'). The description does not explain how latitude, longitude, or timezoneOffset influence output, nor what the date represents (e.g., birth date). The example shows only date, leaving ambiguity.

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 'Real estate, family home, ancestry' clearly specifies the domain of this palace tool. The title 'Property Palace (Tianzhai)' aligns with the description, and it is distinct from sibling palace tools (e.g., health, career, wealth) by focusing on property and ancestry.

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?

No explicit guidance on when to use this tool versus other palace tools or alternatives. The context of sibling names implies its purpose, but the description does not state conditions or exclusions, leaving the agent to infer usage.

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