图片旋转

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

The annotations only signal readOnly=false and destructive=false, so the description adds useful behavioral context: positive angles mean clockwise, output is always a base64 PNG, and output_path is an optional save location. It clarifies the side-effect boundary without contradicting any annotation.

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 compact and front-loaded with the core action, followed by a short parameter list and a return-value line. It is slightly repetitive of the schema, but remains scannable and free of unnecessary prose.

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 straightforward rotation tool, the description plus full schema coverage and annotations cover required parameters, angle convention, optional output, and return format. Minor gaps such as error handling or alternative-tool routing do not significantly hinder correct invocation.

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%, so the baseline is 3. The description mostly repeats what the schema already says about angle direction and output_path behavior, only adding example angles (90/180/270/45). It does not introduce meaningful new parameter semantics.

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 opens with '旋转图片指定角度' (rotate an image by a specified angle), clearly identifying the action, resource, and key parameter. It is sufficiently distinct from sibling operations like resize, crop, and flip, though it does not explicitly reference any sibling tool.

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 details parameters and return behavior but provides no guidance on when to choose rotation over sibling tools such as image_flip or image_crop. In a context with multiple image transformation siblings, the absence of explicit routing or exclusions leaves selection to inference.

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