select_auspicious_date

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it offers no details about output format, limitations, or side effects. It only mentions that it selects dates, without explaining the selection process or result structure.

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 a single, direct sentence with no redundant wording. It front-loads the main function ('择日功能') and is appropriately sized for a clear purpose.

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?

Given the tool has 4 parameters, nested objects, and no output schema or annotations, the description is under-specified. It does not explain expected return values, how different event types affect selection, or how the date range is used, making it incomplete for an agent to invoke confidently.

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 adds little beyond the schema. It mentions 'personal birth chart' and 'auspicious days,' which loosely maps to chart and dateRange, but it does not clarify eventType, timePreference, or the dateRange constraints. With 75% schema coverage, the missing top-level dateRange description is not compensated.

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's function: '择日功能，根据个人命盘选择适合的吉日良辰' (date selection function, selects auspicious days/times based on personal birth chart). It has a specific verb (select) and resource (auspicious dates), and it distinguishes itself from sibling tools like analyze_fortune or generate_chart by its focus on date selection.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It only states what the tool does, leaving the agent to infer usage context.

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