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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is partly covered. The description adds no context about what is destroyed (existing individual corner values), what happens to non-rectangular shapes, or whether the operation is undoable, so it contributes almost nothing beyond the structured fields.

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?

It is a single front-loaded sentence with no wasted words, but its brevity comes at the cost of under-specification rather than true efficiency.

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 destructive mutation with two undocumented parameters, no output schema, and no schema descriptions, the description is far too thin. Annotations cover idempotency and destructiveness, but an agent still cannot tell what radius formats are valid or precisely which shapes are affected.

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%, so the description must carry parameter meaning. 'one corner radius' hints that the radius parameter applies uniformly to all corners, but the accepted formats (string vs number, units) and the shape_ids selection semantics are left unexplained.

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 sentence conveys the effect (assign one uniform corner radius) but the verb 'give' is vague and the resource is described as 'rectangles' while the parameter is generically 'shape_ids'. It does not say that existing per-corner radii are overwritten or how this differs from the sibling normalize_spacing beyond the nouns.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as normalize_spacing or set_style. The agent must infer the use case entirely from the tool name.

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