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

Annotations already convey destructive, non-read-only, and idempotent behavior. The description adds the login requirement and explicitly explains the no-op behavior when no rating exists, which complements the idempotentHint annotation. No contradictions with annotations are present.

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 compact sentence with no filler. It front-loads the login requirement, then states the action, scope, and idempotency behavior, making every part informative.

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 simple two-parameter delete operation with rich annotations covering destructive and idempotent behavior, the description is complete. It includes authentication needs, target scope, and the no-op edge case, so an agent has all necessary context to invoke the tool correctly.

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 both targetType and targetId are already documented. The description clarifies that the target can be a product, park, or manager, which aligns with the enum, but adds little beyond what the schema provides. Baseline 3 is appropriate given full schema coverage.

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 uses a specific verb ('删除' delete) and a specific resource ('当前用户对某对象的评价' the current user's rating for a target). It clearly distinguishes this from sibling tools like rate_product, which creates a rating, and delete_need, which deletes a need rather than a rating.

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 states that login is required and that the operation is idempotent, which gives clear context for when to call it. It does not explicitly name alternative tools or exclusion cases, but the context is sufficient for an agent to understand this is the deletion counterpart to rating operations.

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