bazi_analyze

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

With no annotations provided, the description carries full burden but only states the action ('分析') without disclosing behavioral traits such as computational requirements, output format, error handling, or any side effects. It's minimal and lacks necessary context for safe invocation.

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, efficient phrase ('分析八字命盘') that is front-loaded and wastes no words. It's appropriately sized for its purpose, though brevity contributes to gaps in other dimensions.

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's complexity (3 parameters, nested objects, no output schema, and no annotations), the description is incomplete. It doesn't explain what analysis produces, how results are structured, or any prerequisites, making it inadequate for informed use by an AI agent.

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 100%, so the schema already documents all parameters. The description adds no meaning beyond the schema, as it doesn't explain parameter interactions or usage examples. Baseline score of 3 applies since the schema handles parameter documentation adequately.

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 '分析八字命盘' (analyze bazi birth chart) states the tool's purpose with a clear verb ('分析') and resource ('八字命盘'), but it's vague about what analysis entails and doesn't differentiate from sibling tools like 'bazi_forecast' or 'combined_analysis'. It provides basic function but lacks specificity.

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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention sibling tools like 'bazi_forecast' for predictions or 'combined_analysis' for broader insights, leaving the agent without context for tool selection.

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