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

Annotations give no hints for read-only, idempotent, or destructive behavior, but they set destructiveHint=false. The description mentions defaults for rotate, vertical, and closeup, which adds some context, but it does not disclose potential side effects like modifying the original creation, whether changes are reversible, or if any assets are destroyed. This is a significant gap since the tool likely mutates the creation.

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 very short and front-loaded with the main purpose in the first sentence. The second sentence lists defaults efficiently. However, given the lack of parameter details, the brevity might be too extreme, but for a two-sentence description it is acceptable.

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 5 parameters, no output schema, and no annotations, the description is inadequate. It does not explain the meaning of parameters, expected input (e.g., creationIdentifier presumably identifies a creation), or return values. It is not complete enough for an agent to use the tool without further assumptions.

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 0%, with 5 parameters. The description only explains the default values for rotate, vertical, and closeup, but does not explain what these parameters mean, their units, ranges, or how they affect the output. It fails to compensate for the absent schema descriptions.

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 states the action (reframe camera around subject) and implies the resource (images). It is clear enough to distinguish from siblings like magnific_images_crop, which also modify images but in a different way. However, it lacks explicit reference to the 'images' resource.

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 (e.g., when to rotate vs. crop). It implies usage for changing camera angle but does not state when not to use or mention any prerequisites (e.g., needing an existing creation).

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