femm_scale_selected

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses almost nothing beyond the mechanical transform. It does not say what happens when no selection exists, whether `session`/`entities` override the current selection, or whether the operation is immediate and irreversible.

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?

A single tight sentence with the verb and its core parameters front-loaded and zero wasted words. It is efficient, though its brevity borders on under-specification for a 4-param mutation tool.

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 mutation tool with no annotations, no output schema, and 0% parameter coverage, this one-liner is inadequate. Two parameters and the selection/targeting semantics are left unexplained, so an agent cannot call it confidently beyond the required `factor`.

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 compensate. It does explain `factor` and `about` (including the default-origin behavior), but `session` and `entities` are entirely undocumented in both schema and description, leaving half the parameters opaque.

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?

States a specific verb (scale) and resource (the selection), with the operation's transformation described precisely via `factor` and `about`. This clearly distinguishes it from sibling selection ops like femm_move_selected, femm_copy_selected, and femm_mirror_selected, though it does not name them explicitly.

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 gives no guidance on when to use this versus the other selection-transform tools (move/copy/mirror). It implies usage from the name alone, with no prerequisites, exclusions, or alternative routing.

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