create_neumorphism

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose a concrete behavior—dual light/dark shadows and matching background—telling the agent this is a visual mutation. It stops short of stating whether existing effects are replaced, whether a visible background is required, or any 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?

One sentence with no filler; the core action and distinguishing shadow technique are front-loaded. Every word earns its place.

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 two-parameter effect tool, the description covers purpose and mechanism and the schema handles parameters. But with no annotations and no output schema, the agent still lacks guidance on prerequisites, effect-replacement semantics, and when to prefer this over other effect tools—so completeness is adequate but not strong.

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% for both nodeId and intensity, so the description does not need to restate parameter meanings. The phrase 'matching background' obliquely supports the background-reading behavior but adds no parameter-level detail beyond the schema. Baseline 3 is appropriate.

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 a specific verb and resource ('Apply neumorphism effect') and defines the technique ('dual shadows (light + dark) with matching background'). This differentiates it from sibling effect tools like create_glassmorphism or generic set_effects without needing to compare schemas.

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?

No sentence states when to use this tool over alternatives or when not to use it. The effect name and sibling list imply a styling-effect intent, but the description itself provides no explicit selection guidance.

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