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

No annotations are provided, so the description carries the full burden. It accurately states that the tool returns a dict with six categories and a disclaimer, and explicitly notes it takes no parameters. However, it does not explicitly disclose that this is a read-only, side-effect-free operation, though this is strongly implied by 'returns'. It is adequate but not richly informative about behavior beyond the return 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 two sentences of minimal length. The main purpose is front-loaded, and the second sentence specifies the return format. There is no wasted wording, and it is appropriately sized for a no-parameter tool.

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 zero-parameter tool with an output schema present, the description is complete: it states what is returned (six tactic types plus a disclaimer) and that no parameters are needed. It doesn't explain the detailed structure of the return, but the output schema covers that. The description is sufficient for an agent to call it correctly and know what to expect.

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 tool has zero parameters, so the baseline is 4. The description reiterates '无参数' (no parameters), which is redundant with the schema but harmless. Since there are no parameters to explain, the description does not need to add meaning; the schema already covers everything.

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 it returns a library of 6 types of psychological pricing tactics, each with principle, when to use, and example. This is a specific verb-resource combination that distinguishes it from siblings like competitive_price_positioning and recommend_pricing_strategy, which focus on positioning and strategy recommendation respectively.

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 mentions that each tactic includes 'when to use' information, but this refers to the content of the returned library, not when to call this tool versus alternatives. There is no explicit guidance on when to use this tool instead of the sibling tools, and no exclusions or alternative recommendations.

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