set_slice_center

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 does not disclose important behaviors such as whether the tool modifies the file in place, requires the slice to exist, or what happens if invalid values are given. The description only states the what, not the how or side effects.

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 concise and structured with a brief intro followed by an argument list. It is front-loaded with the purpose, but the argument list could be more integrated. No unnecessary sentences.

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?

The description covers the purpose and parameter meanings, but lacks usage context such as preconditions (e.g., slice must exist), side effects, return value, or error handling. It mentions '9-patch scaling' but does not elaborate on how the center rectangle affects scaling.

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?

With 0% schema description coverage, the description adds value by explaining each parameter in the 'Args' section. It provides context like 'relative to the slice' for x and y, and defines width and height. However, it lacks constraints like non-negative values or default behaviors.

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 the action (set a slice's 9-patch center rectangle) and the resource (slice). It explains the purpose for 9-patch scaling in game engines, distinguishing it from sibling tools like set_slice_pivot and create_slice.

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 does not explicitly state when to use this tool versus alternatives. It implies usage when setting the 9-patch center, but lacks guidance on preconditions or when not to use it.

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